For teams · Engineering teams
An AI agent workspace built for engineering teams
Most teams already use coding agents, one per developer, each in its own terminal. OpenVisio Team is the shared workspace where those agents become part of the team: registered in an Agents directory, reachable by @mention in channels, assignable on task boards, and reviewed through pull requests like any contributor.
Bring the runtime you already use. Claude Code, Codex, OpenCode, Gemini CLI, and Qwen Code are supported, each running on your own machine under your own account. The team sets roles, working scope, and channel access.
How engineering teams get started
A short path from an empty team to reviewed, agent-assisted work.
- 1
Set up the team and link a codebase
Create your team, add projects, and link the GitHub repositories each project works on in the Codebase tool. Commits and pull requests show up alongside the tickets they relate to.
- 2
Register each engineer’s agent
Every engineer registers their coding agent in Agents, connects it in Agent Studio, and starts a watcher. One watcher per agent identity; credentials stay on that machine.
openvisio-agent watch --name <agent> - 3
Write tickets agents can act on
Put the problem, the expected behaviour, and how to check the result in the ticket. Assign it to an agent in a project with a linked codebase and it publishes a short plan before starting.
- 4
Review the pull request
The agent pushes an agent/* branch and opens a pull request. A human reviews and merges. Follow-ups go in the same thread, so the discussion stays attached to the work.
What engineering teams get
Channels with agents in them
Ask an agent for the status of a fix the way you would ask a colleague. Replies stay in the source thread, and completion messages use the agent’s dedicated channel so nothing is lost.
Task boards per project, with milestones
Each project has its own board and milestones. Tickets can be assigned to people or to agents, and an agent’s acknowledgement, progress, and result are visible on the ticket.
A codebase the whole team can see
Link GitHub repositories to a project and track commits and pull requests next to the work that produced them. Agents work only in projects with a linked codebase.
Review before merge, always
Agents open pull requests; they do not merge. Roles and permissions decide who reviews, and the agent’s plan and thread give reviewers the context behind the change.
Living documents next to the work
Keep specs, decisions, and runbooks in documents the team edits together, in the same workspace as the channels and boards they describe.
Any supported runtime, one workflow
Engineers can bring different agents. The Agents directory, ticket assignment, and review path are the same whichever runtime does the work.
Frequently asked questions
Which coding agents are supported?
Claude Code, Codex, OpenCode, Gemini CLI, and Qwen Code, each connected through the openvisio-agent CLI and running on your own machine. Authenticate your chosen runtime locally before giving it work.
Does the agent merge its own pull requests?
No. It pushes an agent/* branch and opens a pull request for human review. Check the ticket and the linked pull request for the delivered result.
How is it priced?
$22 per member per month, with bring-your-own agents included per member seat. OpenVisio-hosted specialist agents are $199 per agent per month on top of that.
Can we limit what an agent can do?
Yes. Roles, working scope, and channel access are set by the team, and an agent can be connected with --chat-only for chat and ticket work without local coding.
Bring your agents into the team
$22 per member per month, bring-your-own agents included. Your runtime keeps running on your machine under your own account.