Agents
Agent workflows that can use your connected tools.
Work with Agents in organization chats your team can share, or in a private chat scoped to you within the organization.
Every Oi Agent chat belongs to an organization and uses that organization's available Contexts, guardrails, connections, and MCP servers. New chats are private to their creator by default. A user must explicitly choose an organization chat before sharing the conversation with other organization members.
Ask an agent to find related GitHub repositories and draft a launch workflow.
Search Zoho leads, pull supporting Contexts, and summarize what should happen next.
Bundle Oi, GitHub, and Linear into one agent workflow for product triage.
Why it matters
Agents turn connected tools into repeatable operating flows.
Customers should not have to wire together a new local MCP setup every time they want useful work done. Oi can centralize the organization's approved connectors, then make them available to the agent workflow that needs them.
Shared chats let organization members work in the same thread and identify who sent each message. Private chats use the same organization resources, but only the creating user can open or continue them.
Connector-backed agent workflows
Let teams build workflows that can look up repositories, search CRM data, inspect docs, and use Oi Contexts from the same request.
Org-scoped MCP access
Connections that are successfully set up for the organization can be bundled as MCP servers for the agent query.
Organization-scoped chat history
Keep shared Agent conversations available to organization members, with each person's messages clearly attributed. Messages sent while the Agent is working join a visible three-place team queue. Private chats remain visible only to their creator inside that organization.
How it works
From org connections to a workflow your team can run again.
Step 1
Connect the tools your team already uses
Bring in approved org connections like GitHub, Linear, Zoho, Google Workspace, and Oi itself so an agent can work with the right systems.
Step 2
Describe the workflow once
Turn repeated requests into an agent workflow with the right context, connectors, instructions, and expected outputs.
Step 3
Choose a team or private org chat
Start with a chat shared across the organization, or make it private to you within that organization when the work should stay personal.
Step 4
Keep every run tied to the org
Agent chats inherit the organization's connections, guardrails, and Context library instead of relying on one person's local setup.