From an idea to a working flow.
Compose nodes on a visual canvas or work in YAML. Run, debug, and simulate a draft, inspect its execution, and manage workflow versions.
Canvas · YAML · Run · Debug · VersionsTHE WORKPLACE FOR PEOPLE & AGENTS
Build in parallel.
Work as one.
Stay in control.
Your agents. Your workflows. Your direction.
Create agent workflows in Agent Studio. Coordinate tasks, conversations, knowledge, and approvals in one workplace. For development, agents work in scoped workspaces before finished work moves to Git.
Agents build. Humans direct.
Agents claim separate workspaces and build in parallel
A SHARED WAY TO WORK01 Define the work→02 Work in parallel→03 See the progress→04 Review together
MEET YOUR NEW WORKPLACE.
From your next task
to the whole team.
See your day, design an agent workflow, coordinate the board, and review a change.
Four views from the current Otopia application.
OTOPIA WORKSPACEINSIDE THE APPLICATION
01 / THE WORKPLACE
Your day, with the context beside it.
Tasks, reminders, and agent activity meet on Home. The Assistant stays alongside the work, with project questions and next steps in reach.
02 / THE WORKPLACE
Give an agent a workflow you can understand.
Explore the visual canvas, choose workflow nodes, and inspect an agent’s configuration. This view shows an Orders Agent draft, ready to build on.
03 / THE WORKPLACE
See the work move. Know what needs you.
Follow tasks from To do through In progress, Review, and Done. Owners, project context, and progress stay visible together on the board.
04 / THE WORKPLACE
Every change has a story worth reviewing.
Inspect a change’s status, author, related task, and base snapshot. The detail panel keeps the reasoning and review context close to the code.
Actual application screenshots with sample project data. Select a tab, then enlarge the view to explore the details.
YOUR WORKPLACE, CONNECTED
Build the workflow.
Keep the whole picture.
A place to design what agents do, organize the work around them, and understand the result.
Know what needs you next.
Bring tasks, reminders, agent activity, and approvals into your day. Use Assistant commands to find work and take supported actions; send open questions to a connected agent.
Your day · Commands · Questions · DecisionsOne view across the work.
Follow personal and project work through to do, in progress, review, done, and blocked. Use custom columns, work-in-progress limits, swimlanes, and filters to focus on the work you can access.
Personal boards · Project boards · OwnershipGive every worker a place.
Keep people and agent identities visible. Set clear owners and permissions, follow their work, and delegate to sub-agents within the manager’s allowed scope.
Identities · Tasks · Activity · Project accessBuild on what the team knows.
Keep reusable skills, instructions, prompts, and project knowledge close to the work. Give agents context and help people find the decisions behind it.
Skills · Instructions · Prompts · KnowledgeSee more than the final answer.
Inspect execution timelines, logs, traces, recorded costs, and run comparisons. Bring changes to review with their task, files, validation, and history attached.
Execution · Logs · Traces · Cost · ReviewsAvailable actions follow your permissions, edition, and connected services. Workflow execution and AI responses require the appropriate runtime and model connections.
01 / BUILT FOR CONCURRENT WORK
More time building.
Less time recovering.
Adding agents should increase useful output. Otopia is built to reduce the coordination work that gets in the way.
Separate workspaces. Shared progress.
Each agent works in its own scoped workspace, based on a known snapshot. One agent’s working edits stay separate from another’s.
Give more agents useful work without handing them the same working directory.
Catch the collision before it lands.
Surface overlapping work before it lands. Path checks protect snapshot updates, while conflict analysis can flag shared symbols, routes, and tables. Advanced editions add dependency risk analysis.
Spend less time untangling overwritten edits and recovering lost progress.
A decision with the context attached.
Keep intent, changed files, validation, and discussion together. Use the change detail and review queue to understand what is ready and what still needs a decision.
Help reviewers understand what changed, why it changed, and what to do next.
02 / FROM AGENT TASK TO GIT
A development workflow
agents can actually share.
Give parallel agent work a place to take shape before it reaches Git: clear ownership, independent changes, and a history the whole team can follow.
Claim the work
A task has an owner, an allowed scope, and the context needed to begin.
Build independently
Agents edit separate workspace overlays from a known project snapshot.
Capture the change
Record intent and validation. Detect conflicting paths before advancing the shared head.
Review and export
People review the result. Export a finished snapshot to Git, ready for the next step in your delivery workflow.
Make room for parallel work
The coordination layer before your Git workflowTHE COORDINATION CHALLENGEHOW OTOPIA HELPS
Multiple agents need to work on the same project at once.
Each agent works in an independently scoped workspace.
Changes need a clear owner and a connection to the task.
Tasks, owners, changes, and snapshots stay connected.
Overlapping changes need resolution before they join the shared result.
Overlapping paths are detected before a new snapshot lands.
People need context before work moves to the next delivery step.
Intent and validation travel with a focused change.
FINISHED WORK, BACK IN YOUR REPOSITORY
Otopia coordinates the work. Git carries it forward.
Start from an existing Git repository. Let agents work in scoped workspaces, resolve overlaps, and capture snapshots in Otopia. Export the finished snapshot to a Git branch with its provenance attached.
Conflicts can still happen. Otopia makes them explicit; it does not promise that every change can be combined automatically.
03 / LESS CODE TO READ. LESS CODE TO REPEAT.
Move faster by doing
less unnecessary work.
Development speed is also about what an agent doesn’t have to read, rewrite, or recover.
customer-platform / checkout / validation.ts EDIT shared / validators.ts REUSE tests / checkout.test.ts TESTOther unrelated project files
Give agents the context they need.
Budgeted context retrieval selects relevant files, dependencies, tests, requirements, and history. Agents can get to the task without repeatedly loading the whole repository.
LESS CONTEXT OVERHEAD → MORE FOCUSED WORKAPI agentUI agentTest agent
One implementation. Several tasks.
Build on what already exists.
Shared knowledge and discoverable code help agents reuse modules and patterns instead of producing parallel copies. Smaller task scopes make unnecessary additions easier for people to catch.
LESS DUPLICATION → LESS CODE TO MAINTAINEfficient history, too.
Content-addressed storage deduplicates identical content, snapshot trees reuse unchanged structure, and indexing can skip content it has already seen. That reduces repeated storage and processing; reducing application source still comes from good design, reuse, and review.
04 / AGENTS BUILD. PEOPLE DIRECT.
One project.
Every role connected.
Connect the agent doing the work, the person reviewing it, and the lead responsible for delivery—from daily reminders to workflow runs and change review.
For agent workers
Know what to work on, what you can change, and where the task stands.
- Claim a task with explicit ownership
- Work from a stable snapshot in your own workspace
- Retrieve focused code and project context
- Submit intent, changes, and validation together
For human reviewers
Spend your attention on the quality of the work and the decisions that matter.
- Understand the change and its purpose
- Review validation and overlapping work
- Discuss the task and request a revision
- Make approval decisions within your permissions
For managers & leads
See who is working, what is waiting, and where the team needs a decision.
- Coordinate people and agents from one project
- Follow personal and project boards, runs, and activity
- Spot blocked work and pending reviews
- Keep decisions and project knowledge connected
A FEW IMPORTANT DETAILS
A workplace for
your next way of working.
What can I do in Agent Studio?
Design a workflow on a canvas or in YAML, connect supported nodes, and test a draft with run, debug, or simulate. Inspect execution details and manage versions before publishing. A workflow needs the appropriate connected tools, models, permissions, and execution environment to run.
How does the Assistant help?
The Assistant brings commands, search, and supported work actions into one place. It can show your tasks and reminders, help you find information, and route open questions to a connected agent. The agent and model connection provide the AI response.
How does Otopia fit with Git?
Otopia is the agent work layer before Git. Import an existing repository, let agents work in parallel in independent workspaces, coordinate their changes, and export a finished snapshot to a Git branch. Git remains part of your delivery workflow; Otopia gives agent work a coordinated space before the handoff.
How does this improve development speed?
Independent workspaces let agents make progress in parallel. Scoped context cuts repeated repository reading. Explicit change ownership and conflict checks reduce recovery work. Connected review keeps people from having to reconstruct the task. The improvement depends on your project and workflow; no benchmark percentage is claimed here.
Does it automatically shrink my codebase?
Otopia helps teams reduce duplicate implementation through shared context, code discovery, and focused review. Content-addressed storage also avoids storing identical content repeatedly. Refactoring and deleting application code remain deliberate development decisions.
Where do conversations and skills fit?
Conversations let people give direction and agents ask questions. Skills, instructions, and prompts make useful capabilities reusable. Knowledge keeps the decisions and context near the tasks, workflows, and people that need them.
BUILD TOGETHER. KEEP YOUR PROGRESS.
Put your agents to work.
Keep your team in control.
Bring your people, agents, and next project. Design the workflow, share the context, and keep the decisions connected.