Repository navigation
Logins
Milimarty edited this page Oct 19, 2026
·
2 revisions
The image has claude, codex, copilot and opencode installed. Nothing from your computer is copied in. Each login is
saved encrypted in keel's own database (the keel-data volume), so it survives restarts and updates.
| Tool | Log in from the dashboard | Or paste |
|---|---|---|
| Claude (subscription) | sign in on claude.com, paste the code it shows |
claude setup-token on your computer |
| Codex (ChatGPT) | open the device link, type the code | ~/.codex/auth.json |
| GitHub Copilot | open github.com/login/device, type the code | a token with "Copilot Requests" |
From the terminal: keel2 token <claude|codex|copilot|anthropic|openai|github>, and keel2 tokens to list them. A long
token is often shown over two lines; send it in one piece from the clipboard: pbpaste | keel2 token claude (Linux:
wl-paste | keel2 token claude). keel checks the token before it saves it and says what is wrong. Connections shows a
subscription as ready only when keel has its login. In native mode keel's agents use their own home, so your own
Claude Code login is not used.
From docs/GUIDE.md · All pages
keel v2
- Home
- How a flow works
- Flows in detail
- Web research
- Rules
- KeelBot
- keel TUI (keel2 tui)
- Thinking effort
- Plugins and the Marketplace
- Stacks
- Plugins: Database, Git and CI/CD
- Quality
- Inbox and run modes
- Usage and caps
- Tasks and Jira
- Logins
- Signing in
- Use keel from Claude Code or Claude Desktop (MCP)
- keel2 commands
- Where keel keeps its files (layouts)
- Native mode (no Docker)
- Docker mode
- Several project folders
- Git worktree projects
- Problems
- Folders in the container
- Without the install script
- Develop keel v2