Context agents
Context agents create, edit, and synthesize files in the context repository through conversational prompts, using the same access as the person prompting them.
Category
Product feature
See all terms
What are context agents?
Context agents are AI agents that create, edit, and manage files inside the context repository through a chat interface. From the Context tab, a user opens the chat, describes what they want, and the agent creates folders, writes new files, edits existing ones, moves files, or deletes what's no longer needed. Agents can also browse and search the repository by meaning or exact text, and combine repository content with synced source data to write consolidated or aggregated documents.
Why context agents exist
Keeping a context repository organized and current is ongoing work: files need restructuring as a workspace grows, and content drawn from synced sources needs to be compared against what's already written and refreshed when it's gone out of date. Doing that by hand means someone has to notice what changed, find every file it affects, and edit each one manually. A context agent does that work from a single prompt instead, reading across the repository and its synced sources to make the edit or write the document directly.
How do context agents work?
An agent operates with the permissions of the person using it and never beyond them, so the same prompt can return different results for different users depending on what each one can access. To use one, open the Context tab, click the chat icon in the top right corner, and type the request.
Every edit an agent makes shows up in the Changes tab with a diff and version history, the same as an edit a person made directly. Files marked "Require review" hold the agent's changes pending approval before they apply; everything else applies automatically. From the chat dropdown, a user can stop an in-flight response, start a new chat, or resume a previous conversation. Because agents read and write directly against the context repository, every change they make becomes part of its version history.