CLI Reference

Synopsis

jailoc [command] [flags]

Global Flags

Commands

jailoc

Auto-detect the workspace from the current working directory. If no matching workspace is found, prompts to add the current directory. If the workspace is not running, starts it. Attaches to the running environment.

jailoc [flags]

When run from a subdirectory of a workspace path, jailoc resolves the current working directory and passes it as --dir to opencode attach, so the agent opens that directory instead of the workspace root.

When neither --remote nor --exec is specified, the connection mode is determined by the workspace mode field in configuration, falling back to auto-detection (checks for opencode, then opencode-cli on PATH). See the access modes how-to for configuration steps, or the access modes explanation for the difference between modes.

jailoc up

Start the Docker Compose environment for the target workspace. No-op if the workspace containers are already running.

jailoc up [flags]

Resolves the container image (see Image Resolution), generates a docker-compose.yml in ~/.cache/jailoc/{workspace}/, and starts two containers: opencode and dind.

When --workspace is not set, resolves the workspace whose configured path best matches the current working directory (longest prefix). Falls back to default. See the workspace configuration how-to for the full resolution order.

jailoc down

Stop and remove the containers for the target workspace.

jailoc down [flags]

Equivalent to docker compose down on the generated compose file. Does not remove named volumes or the image.

When --workspace is not set, resolves the workspace whose configured path best matches the current working directory (longest prefix). Falls back to default. See the workspace configuration how-to for the full resolution order.

jailoc restart

Stop and restart the Docker Compose environment for a workspace.

jailoc restart [flags]

Equivalent to jailoc down followed by jailoc up. Regenerates the compose configuration from the current config.toml before bringing the workspace back up. If the workspace is not running, starts it without error.

When --workspace is not set, resolves the workspace whose configured path best matches the current working directory (longest prefix). Falls back to default. See the workspace configuration how-to for the full resolution order.

jailoc status

Print the state and assigned port for each configured workspace.

jailoc status [flags]

Output shows the container state (running, stopped, or unknown) and the assigned host port for the resolved workspace. Workspaces with expose_port = false show "not exposed (exec-only)" instead of a port number.

When --workspace is not set, resolves the workspace whose configured path best matches the current working directory (longest prefix). Falls back to default. See the workspace configuration how-to for the full resolution order.

jailoc logs

Stream container logs from the target workspace environment.

jailoc logs [flags]

Streams combined stdout and stderr from the opencode and dind containers. Follows log output until interrupted.

When no positional workspace argument and --workspace is not set, resolves the workspace from the current working directory (longest prefix). Falls back to default. See the workspace configuration how-to for the full resolution order.

jailoc config

Print the current resolved configuration.

jailoc config [flags]

Reads ~/.config/jailoc/config.toml, resolves all defaults and ~ expansions, and prints the result. Useful for verifying what values are in effect.

jailoc add

Add the current working directory to the target workspace's paths list.

jailoc add [flags]

Appends the current directory to workspaces.<name>.paths in ~/.config/jailoc/config.toml. The path must not be under a forbidden system prefix. See the configuration reference for path validation rules.

When --workspace is not set, resolves the workspace from the path being added (longest prefix). If --workspace is set explicitly and the path is not under any of that workspace's configured paths, jailoc add returns an error. See the workspace configuration how-to for the full resolution order.

Update Checks

jailoc checks GitHub Releases for newer versions on every command run. The check runs asynchronously in the background and does not block command execution.

Behavior

• Frequency: Cached for 24 hours. Subsequent checks within the cache window return the cached result.
• Output: When a newer version is available, a notice is printed to stderr. If stderr is not a TTY (e.g., when output is redirected or piped), the notice is suppressed, but the background check still runs and updates the cache.
• Non-blocking: The check runs in a goroutine and results are collected at command completion. Command execution is not delayed.
• Color: Respects the --no-color flag. When --no-color is set and a notice is printed, it appears without ANSI color codes.

Disabling Update Checks

Update checks are skipped in the following conditions:

• Development builds: Builds whose version is dev or (devel) (e.g., local go build without release ldflags)
• CI environments: When the CI environment variable is set to any non-empty value
• Explicit opt-out: When the JAILOC_NO_UPDATE_NOTIFIER environment variable is set to any non-empty value

To disable update checks, set the environment variable:

export JAILOC_NO_UPDATE_NOTIFIER=1
jailoc up

Environment Variables