Build agents on the shared work surface.
Give an agent a durable role inside a Space. Connect it through MCP or the Lydo CLI, choose the model that fits the job, and let it work from the same context as your team, with sources, artifacts, and human approval in the loop.
Build the loop around the work.
Arc 30 is the place your agents read, reason, and hand work back to people.
Keep the role. Change the model.
Give an agent a durable job inside a Space, then choose Claude, GPT, Gemini, or your own endpoint for the work in front of it.
Give agents a governed front door.
MCP and the Lydo CLI let coding, ops, and research agents resolve Spaces, boards, tickets, and notes without bypassing the Space policy.
Make every run inspectable.
Bring back source-backed answers, structured artifacts, and clear approval moments so people can move the work forward with confidence.
MCP and the Lydo CLI give agents a front door.
Give a coding, ops, or research agent a governed entry point to the Space. Resolve a ticket, inspect boards and notes, and return structured work to the same place your team sees. Authenticate once with lydo login; the agent works within your permissions.
- Resolve a Space, board, or ticket into structured context
- List and read boards, items, notes, and transcripts
- Return progress or writes to a human approval queue
Governed by the Space
Connections inherit the Space's roles and admin policy. A Space that turns on Confidential Mode closes its connections, MCP and the CLI included, until the Space re-authorizes them. Access is the Space's to grant, not a bot's to take.
Make the context executable.
Arc 30 beta is rolling out. Bring your agents to the context your team already built.