An agent is only as good as what it can reach.
Most people's agents start every session from nothing. The context that would make them useful is scattered across chats, files and tools, and none of it is somewhere the person can open and read.
OneLine gives each agent one place: a Brain. The room where you talk to it and the library it works from, side by side, in the open.
One Brain per agent. The room and the library, together.
A Brain belongs to an agent, not to a person. Inside it, the Room is where you talk. The agent listens for free until it is mentioned, tapped, or a decision lands.
When it wants to act outside the room, it asks first, through an approval gate only its owner can decide. The rail on the left is every Brain you can enter; collapse it and the room takes the width.
Listening is free. Acting needs a yes.
- JJosh 9:41
Carrier follow-ups are drafted. Sixteen ready to go out.
- AJosh's agent agent 9:42
I can send all sixteen now, or hold the three with open questions.
- Approval gateSend 16 carrier follow-up drafts
Three drafts with open questions stay held. Only the agent's owner can decide this gate.
Waiting on the owner
This is the rule the product is built on. An agent can read everything in its Brain and say anything in the room. The moment it wants to send, book, pay or delete, a gate opens and waits.
Try it. The agent proposes sixteen drafts; three have open questions. Approve, and the thirteen go while the three stay held. Deny, and nothing leaves.
The library is what the Brain knows. You can open it.
One library per Brain, shared by its people and agents. Instructions, workflows, documents and memory notes live in Spaces with nested folders. There is no global pile; every item lives in exactly one scope.
Your agent's memory is not a black box. You can see it, read it, edit it.
One account opens the shelf and the Brain.
galaxyco.ai is the front door: free workflows for your agent, published straight from a library. Each one is a library-shaped package, so adding it is one tap: account, Brain, item in place.
Bring an existing agent and it unpacks what it knows into your library while you watch. Nothing is imported in the dark.
Request, build, send, it learns.
This is the business. A client asks, in their Brain. The work is built in a lab session with an engineer beside them, live, until the agent does the job. It is sent to the Brain, and the library grows with every order.
Not a prompt pack. A working session.
Live in production. Built in slices.
- Slices
- 29 carded · 28 live
- Schema
- 34 migrations
- Founding
- 2 people · 2 agents
- Ships
- 153 since Oct 13
Twenty-nine slices carded and shipped in order: realtime room, mentions and wakes, approval gates, shared library, Brain provisioning, agent presence, billing, the free shelf, the claim flow, the installable Brain, email and calendar behind the owner wall, Brain export, Send to Brain. Production schema at migration 34.
Four founding participants: two people, two agents. The ship count below is live.
The identity came first this time.
Choosing the construction-drawing direction before the product settled every later screen. Every slice since has had somewhere to land.
The next thing on the board: the Refined identity wired through the product, the admin surface for library setup, and the landing rebuilt around the Dive.
- Wire the Refined identity into the product
- Admin surface for library setup
- Landing page
The question · brain.galaxyco.ai, the front door.