-
Notifications
You must be signed in to change notification settings - Fork 0
Known Hiccups
These are known first-use issues that can look like hard failures but are usually one-time setup friction.
aicage runs agents inside a container. Authentication methods that try to open a browser directly from the
container often do not work on the host machine.
Use authentication options that give you a URL and code to open manually on the host. In Codex CLI, choose
Sign in with Device Code instead of browser-driven login from inside the container.
This is typically a one-time setup per agent.
If no Claude config exists on the host yet, ~/.claude.json may be created as an empty file on first run. Claude
then reports a JSON parse error.
Fix:
- Choose
Reset with default configurationin Claude's prompt. - Continue setup.
After this reset, future runs should start normally.
When using Linux containers on Windows, Git can show unexpected diffs if line-ending conversion is not configured on the host.
Set this on the Windows host:
git config --global core.autocrlf trueThis prevents many CRLF/LF mismatch diffs in shared workspaces.
Some agents, including OpenCode, write clipboard content through OSC 52 escape sequences. In tmux this may need explicit clipboard support enabled first.
Add this to ~/.tmux.conf:
set -s set-clipboard on
set -as terminal-features ',*:clipboard'
Restart tmux after updating the config.
If OSC 52 clipboard writes do not work in Git Bash on Windows, add this to ~/.minttyrc:
AllowSetSelection=yes
Restart Git Bash after updating the config.
aicage has CI coverage for macOS startup paths, but it is not regularly tested on real macOS user machines.
If you use native Docker on macOS and aicage does not start cleanly, please open an issue and include debug output.
Treat this as best-effort support for now.