Context UnifyConnections for people and agents
Connect your agents to your tools
Each person connects their own accounts, admins register your internal services, and agents search every file the person can open.
Connect your accounts
Manage connectorsConnect the tools your agents can use on your behalf. CLI tools like GitHub and AWS are connected in Settings → Connectors.
Apps
Connect your accounts
Connect the tools your agents can use on your behalf. CLI tools like GitHub and AWS are connected in Settings → Connectors.
Apps
Connect the apps your team uses
Each person connects their own Slack, Google Workspace, Salesforce or GitHub account, and agents act with that account.
Connect your accounts
Manage connectorsConnect the tools your agents can use on your behalf. CLI tools like GitHub and AWS are connected in Settings → Connectors.
Apps
Register your internal services
An admin registers an HTTP or MCP service once and chooses which workspaces can use it.
Register Connector
Define a connector with its tools. Form and YAML edit the same manifest.
- 1Connector
- 2Access
- 3Authentication
- 4Tools
Search every file you can open
People and agents search inside the folders you choose, with results limited to files the person can open.
AI search
Which folders people and agents can search inside, and how deeply.
| Folder | Files | Depth | Last refreshed |
|---|---|---|---|
| Q3 portfolio review deck | 1,284 | Deep | 4m ago |
| Projects | 612 | Organization default | 12m ago |
| Shared with team | 96 | Organization default | Getting ready · 41 of 96 files |
Connect the tools your team uses
Every person connects their own accounts from one directory, so an agent reaches only what that person can.
Connect your accounts
Manage connectorsConnect the tools your agents can use on your behalf. CLI tools like GitHub and AWS are connected in Settings → Connectors.
Apps
Connect your accounts
Connect the tools your agents can use on your behalf. CLI tools like GitHub and AWS are connected in Settings → Connectors.
Apps
Register your own services
Describe an internal service once as a connector, with its tools, its sign-in and who can use it.
Register Connector
Define a connector with its tools. Form and YAML edit the same manifest.
- 1Connector
- 2Access
- 3Authentication
- 4Tools
Register Connector
Define a connector with its tools. Form and YAML edit the same manifest.
- 1
- 2Access
- 3
- 4
Search inside your files
Choose which folders people and agents can search inside, and how deeply, with every result checked against the person's permissions.
AI search
Which folders people and agents can search inside, and how deeply.
| Folder | Files | Depth | Last refreshed |
|---|---|---|---|
| Q3 portfolio review deck | 1,284 | Deep | 4m ago |
| Projects | 612 | Organization default | 12m ago |
| Shared with team | 96 | Organization default | Getting ready · 41 of 96 files |
AI search
Which folders people and agents can search inside, and how deeply.
| Folder | Depth |
|---|---|
| Q3 portfolio review deck | Deep |
| Projects | Organization default |
| Shared with team | Organization default |
Secure by default
Agents act with the connecting person's account and permissions, and every connection they make crosses a checkpoint outside the sandbox.
How access works
- Atlas can only see channels it has been added to.
- Everything Atlas does is recorded under its name, with the task it was working on.
Approvals
Always allowed
Things you have told this agent it can always do, so it stops asking. Remove one and it goes back to asking.
How access works
- Atlas can only see channels it has been added to.
- Everything Atlas does is recorded under its name, with the task it was working on.
Approvals
Always allowed
Things you have told this agent it can always do, so it stops asking. Remove one and it goes back to asking.
Use your connections on any device
Connect an account once and use it from the web, the phone apps, the desktop app or the terminal, with the same permissions everywhere.
Connect your accounts
Manage connectorsConnect the tools your agents can use on your behalf. CLI tools like GitHub and AWS are connected in Settings → Connectors.
Apps
Connect your accounts
Connect the tools your agents can use on your behalf. CLI tools like GitHub and AWS are connected in Settings → Connectors.
Apps
Work across the Context platform
Workspace is where your people and agents work, Engine runs it, Unify connects it to your tools, and Evals makes it better.
- WorkspaceChat, files and tasks where your people and agents work, with every connection available in the composer.
- EngineThe models and sandboxes your tasks run on. Connector calls leave the sandbox through one checkpoint.
- EvalsScore each run that used your connectors against your criteria, and track pass rate and cost per agent.
- DriveFiles your team stores in Drive are searchable by meaning, limited to the files each person can open.
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Home
- q3-portfolio-review.pptx1h ago
- q3-valuation-bridge.xlsx2h ago
- q3-portfolio-updates.docx3h ago
- lp-letter.pptx5h ago
Deploy in your environment
Run Unify inside your own deployment, where connectors can reach internal services over a private network.
- Inside your deploymentConnector calls and search run inside your own deployment, on your cluster.
- Private network routesRoute a connector to an internal service over a private network instead of the internet.
- Self-hosted through KOTSInstall Context in your own environment with KOTS self-hosting.
- Your identity providerSign people in with SAML or OIDC and provision them with SCIM.
Context runs in production at Qualcomm. Read the case study
- Amazon EKS
- Azure AKS
- Slack
- Air-gapped
Context Unify is included in every Context workspace, including the Free plan.
- Free$0Includes Context Unify
- Plus$20Per person per month
- EnterpriseCustomEnterprise deployments run in your own cloud.Talk to us about a plan
Questions
Whose account does an agent use?
The account of the person the agent works for. Each person connects their own accounts, so an agent reaches only what that person can.
Can we connect an internal service?
Yes. An admin registers it as a connector over HTTP or MCP, with its tools and its sign-in, and chooses whether the whole organization, specific workspaces or only they can use it.
Which sign-in methods does a custom connector support?
None, a bearer token, an API key header, an HMAC-SHA256 signature or OAuth 2.
Can a connector reach a service that is not on the internet?
Yes. A connector can route to an internal service over a private network instead of the internet.
Does search show files I cannot open?
No. Results are filtered by permissions before they appear, for people and for the agents working for them.
How does Slack work with Context?
An admin turns on the Slack connector for the organization and binds a Slack channel to a Together channel. Every message in the bound channel then arrives in Together, where your agents can answer.



