co ai Delegates to Codex and Claude Code — and You Watch It Work
ConnectOnion 1.7.0 is stable: live resumable Work Room, three plain permission modes
ConnectOnionBack to DocsDesign Journal
Design decisions, lessons learned, and the thinking behind the framework.
ConnectOnion 1.7.0 is stable: live resumable Work Room, three plain permission modes
Not a smarter model — an agent you can safely stop watching
Standing permission still matters when nobody can answer a dialog
Malformed tool text should not become a fatal upload
A stable fix cannot disappear from the next preview
Pick a region, share an address without handing over a key — ConnectOnion 1.6.12
Conversation, live work, permissions, and input inside one remote-client shell
A safe coding surface shows the next useful fact without pretending to be a terminal or a screenshot
A careful nested approval should not spend a native coding turn’s work budget
How long-running native coding work stays observable without turning chat into a terminal dump
Secure defaults still need a private recovery path
Finite mailbox pages that never hide the rest of the data
Gemini 3.7 Flash by default, and why the client shipped second
What a deployed process should inherit, and what it must not
One web boundary, native providers, and rolling upgrades
Safer remote agents and a cleaner credential boundary
From Complexity to Clarity
The Story Behind ConnectOnion's Authentication Keyword
Functions Need Verbs
The Power of User Mental Models
Why Hex-Encoded Public Keys
The Power of Precise Naming
Simplicity First, Power When Needed
Writing in public
How we built the eval system — session replay without adding a line of user code
The trust model — why agent-to-agent auth is harder than you think
Plugin architecture internals — hooks, lifecycle, and the 9 event types
If ConnectOnion saves you time, a ⭐ goes a long way — and earns you a coffee chat with our founder.