ConnectOnion's co CLI hands your coding agent Gmail, Slack, Calendar, Linear and a logged-in browser without one MCP server per tool.
Yes, ConnectOnion (one CLI that gives coding agents your inbox, calendar, chat and browser) is open source under the Apache-2.0 license.
Free (Apache-2.0) with your own model keys or Ollama. Optional managed keys with a '$5 credit' starter (vendor claim); co search uses paid credits unless BYO key or --engine ddg. (freemium).
Yes, ConnectOnion (one CLI that gives coding agents your inbox, calendar, chat and browser) can be self-hosted (the source is available under the Apache-2.0 license).
**ConnectOnion** (openonion/connectonion) is an **Apache-2.0** agent CLI harness. Its co command gives a coding agent (Claude Code, Codex, Cursor and others) access to Gmail, Outlook, Google Calendar and Meet, OneNote, Slack, Teams, WhatsApp, Telegram, Discord, SMS, Google Drive, Linear, Canny, a logged-in Chrome, web search and fetch, SSH and schedules, all through one command line.
The README's argument is against loading a schema per tool: an MCP server or plugin puts every tool definition into the prompt, while co loads nothing up front and the agent finds each command through --help when it needs it. Commands that change something preview until you pass --yes. Credentials stay in ~/.co/keys.env or are encrypted with co env set --secret. co rem keeps a local Markdown notebook built from mail and coding sessions.
It installs with pip install connectonion (Python 3.11+) or an install.sh script that uses uv, and accepts your own keys for OpenAI, Anthropic, Gemini, Mistral, Groq, Grok and OpenRouter, or a local Ollama model.
A RevOps operator who already uses Claude Code for internal jobs can let the same agent triage an inbox, check a calendar, post a Slack update or open a Linear ticket, with a preview before anything is sent, instead of wiring and maintaining one integration per tool.