readme: Remove broken Claude Pro/Max bridge docs and mention local aliases
This commit is contained in:
parent
1b35ab0b2a
commit
6c859eb427
1 changed files with 1 additions and 31 deletions
32
README.md
32
README.md
|
|
@ -8,9 +8,9 @@ Run OpenCode, Claude Code, and Pi (pi.dev) inside a shared Arch Linux Docker con
|
||||||
- Runs as the host user (same username, UID, GID)
|
- Runs as the host user (same username, UID, GID)
|
||||||
- **Per-project isolation**: Each project gets its own container (identified by project path hash)
|
- **Per-project isolation**: Each project gets its own container (identified by project path hash)
|
||||||
- **Shared persistent home**: All containers mount the same home directory from XDG_DATA_HOME, allowing tools and credentials to persist across projects
|
- **Shared persistent home**: All containers mount the same home directory from XDG_DATA_HOME, allowing tools and credentials to persist across projects
|
||||||
- **Unified home**: Both tools share the same `$HOME`, enabling plugins like [opencode-claude-bridge](https://github.com/dotCipher/opencode-claude-bridge) that need access to both tools' config
|
|
||||||
- **Sudo access**: Agents can install project-specific dependencies that persist in the stopped container
|
- **Sudo access**: Agents can install project-specific dependencies that persist in the stopped container
|
||||||
- **Hard linking support**: Can hard link files like `~/.gitconfig` to share configurations with containers
|
- **Hard linking support**: Can hard link files like `~/.gitconfig` to share configurations with containers
|
||||||
|
- **Local variants**: `opencode-local`, `claude-local`, and `pi-local` run the tools directly on the host, bypassing the container
|
||||||
- Mounts only the current project directory (same absolute path inside container)
|
- Mounts only the current project directory (same absolute path inside container)
|
||||||
- **Security boundary**: No access to SSH keys, passwords, or full `$HOME` (intentionally prevents remote code pushes)
|
- **Security boundary**: No access to SSH keys, passwords, or full `$HOME` (intentionally prevents remote code pushes)
|
||||||
|
|
||||||
|
|
@ -97,33 +97,3 @@ ln ~/.gitconfig ~/.local/share/agent-container/container-home/.gitconfig
|
||||||
|
|
||||||
Avoid linking sensitive files such as `~/.ssh/id_*` or `~/.gnupg/` -- keeping those out of the container is an intentional security boundary.
|
Avoid linking sensitive files such as `~/.ssh/id_*` or `~/.gnupg/` -- keeping those out of the container is an intentional security boundary.
|
||||||
|
|
||||||
## Optional: Use Claude Pro/Max with OpenCode
|
|
||||||
|
|
||||||
The [opencode-claude-bridge](https://github.com/dotCipher/opencode-claude-bridge) plugin lets OpenCode use your Claude Pro/Max subscription via the Claude CLI's OAuth credentials. Because both tools share the same `$HOME` inside the container, the bridge can read Claude's credentials directly.
|
|
||||||
|
|
||||||
1. Run Claude Code inside the container and log in to your Max account:
|
|
||||||
|
|
||||||
```sh
|
|
||||||
claude
|
|
||||||
```
|
|
||||||
|
|
||||||
Complete the login flow. This creates the credentials file at `~/.claude/.credentials.json` inside the container home.
|
|
||||||
|
|
||||||
2. Create the OpenCode config to enable the plugin:
|
|
||||||
|
|
||||||
```sh
|
|
||||||
mkdir -p ~/.local/share/agent-container/container-home/.config/opencode
|
|
||||||
cat > ~/.local/share/agent-container/container-home/.config/opencode/opencode.json << 'EOF'
|
|
||||||
{
|
|
||||||
"plugin": ["opencode-claude-bridge"]
|
|
||||||
}
|
|
||||||
EOF
|
|
||||||
```
|
|
||||||
|
|
||||||
3. Start OpenCode:
|
|
||||||
|
|
||||||
```sh
|
|
||||||
opencode
|
|
||||||
```
|
|
||||||
|
|
||||||
Press `Ctrl-p`, select **Switch Model**, and Anthropic will appear as a provider.
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue