If you run Claude Code, Codex or OpenCode across several accounts and repositories, Olivares puts them on a machine you own, in one web console. The CLI and the API work on the same engine.
One command
curl -fsSL https://olivares.ai/olivares/install.sh | sh
olivares quickstart
quickstart prints the console address and a one-time token for your administrator account.
Your tools and accounts
Install the tools from the AI tools page and run local models through Ollama. Sign in your Claude Code accounts from the browser or add API keys; the page shows each account's plan and usage windows. Installed here lists what a new session receives: tools, skills and MCP servers.
the AI tools page.
signing in Claude Code.
Sessions
- Sessions in parallel, each in its own git worktree if you want.
- Type
/for the commands, skills and agents the tool reports. - Replies read as formatted text, with lists, code and tables.
- Approve the exact command before it runs.
- One Claude Code account out of quota: move the session to another.
- Hand off to any tool with a summary of the conversation.
- Close the terminal; the session keeps running.
Skills and MCP servers
Install skill packs from the console, give them to a workspace, folder or session, and pin an earlier revision to roll back. MCP servers can go to only the sessions that need them.
Scriptable
olivares login
olivares session start . --name first-hour
olivares session send first-hour "Explain this project."
olivares session follow first-hour
Your record
Every decision goes into a signed log you can verify, and one switch stops every agent. There is no mandatory telemetry.
If a command doesn't behave as the docs say, we treat it as a bug: open an issue.
- Repo: https://github.com/olivaresai/olivares
- Web: https://olivares.ai
- Docs: https://docs.olivares.ai
- https://youtu.be/V599Pf-j6gU
Top comments (0)