AI Terminal Sessions
MultiDocker can spawn project-scoped terminal sessions running an AI coding tool, a
plain shell, or a shell inside one of the project’s containers. Each session is a
detached tmux session, so it keeps running after you close the app and you can
re-attach later.
Available tools
Section titled “Available tools”| Tool | What it runs |
|---|---|
claude |
Claude Code (claude, or claude --sandbox in sandbox mode). |
copilot |
GitHub Copilot CLI (gh copilot if the extension is installed, else copilot). |
shell |
Your login shell in the project directory. |
exec |
A shell inside a project container via docker compose exec. |
Check which tools are installed on your machine:
mdocker terminal tools # JSON list with availability per toolCreate and manage sessions
Section titled “Create and manage sessions”mdocker terminal new aurora --tool claude # start a Claude Code sessionmdocker terminal new aurora --tool claude --sandbox # sandbox modemdocker terminal new aurora --tool shellmdocker terminal list aurora # list sessionsmdocker terminal kill aurora <session-id> # end one sessionmdocker terminal prune aurora # drop dead registry entriesSessions are named mdocker__<project>__<id> in tmux, and their state lives under
.projects[<name>].sessions[] in the registry.
Container shell (exec)
Section titled “Container shell (exec)”To open a shell inside a running container, use terminal exec. It builds the correct
docker compose exec invocation for the project’s COMPOSE_FILE stack:
mdocker terminal exec aurora shop # bash (default) in the shop containermdocker terminal exec aurora db sh # a specific shellWhere sessions start
Section titled “Where sessions start”By default a session opens in the project directory. You can set a per-project start
path (absolute, ~/-relative, or relative to the project), and a separate
“open in editor” path:
mdocker terminal path aurora # show the current start pathmdocker terminal path aurora ./backend # set itmdocker terminal editor-path aurora ~/Projects/auroraAttaching from the macOS app
Section titled “Attaching from the macOS app”The app lists a project’s sessions and attaches to them via SwiftTerm. Because the sessions are real tmux sessions, they survive an app quit and can be re-attached later. See Attached Terminals.
Related
Section titled “Related”Cookie settings
We only use statistics tools if you allow it. Necessary storage keeps this site working; everything else is off until you decide.
Stores your choice from this dialog in your browser (localStorage). No cookie, no transfer to third parties.
Google Analytics 4 via Google Tag Manager, to measure how the site is used. Loaded only after you allow it.