Does dc-try edit my repo?

No. Override JSON lives under $XDG_STATE_HOME/dc-cli/try/ /. git status stays clean.

When should I use dc-up instead?

When .devcontainer or a root compose file already exists. dc-try refuses those and points you at dc-up.

go (go.mod), python (pyproject.toml / requirements.txt / Pipfile), node (package.json). Exactly one signal wins. Zero or many → generic base image.

Does it publish ports?

Yes — default localhost ports by profile (node 3000/5173, python 8000/5000, go 8080, generic 3000/8080), then dc-forward. Skip with --no-forward. A real .devcontainer still wins for custom ports.

guide / try· 2026-08-20

No config yet. Still get a shell.

dc-try is the growth path for folders that would otherwise be kind=none.

Command	Does
`dc-try --print .`	write override + print; do not start
`dc-try .`	confirm, then start
`dc-try --yes .`	start without prompt (TUI / agents)
`dc-try --no-forward .`	start without sidecar port publish
`dc-try --profile node .`	force a profile

cd /path/to/plain-repo
dc-try --print .
dc-try .
dc-exec .
dc-down .

TUI u / start on a configless folder asks y/n, then runs dc-try --yes.

FAQ

Does dc-try edit my repo?: No. Override JSON lives under $XDG_STATE_HOME/dc-cli/try/<hash>/. git status stays clean.
When should I use dc-up instead?: When .devcontainer or a root compose file already exists. dc-try refuses those and points you at dc-up.
What profiles exist?: go (go.mod), python (pyproject.toml / requirements.txt / Pipfile), node (package.json). Exactly one signal wins. Zero or many → generic base image.
Does it publish ports?: Yes — default localhost ports by profile (node 3000/5173, python 8000/5000, go 8080, generic 3000/8080), then dc-forward. Skip with --no-forward. A real .devcontainer still wins for custom ports.

Broke something?report it