CI Fixer
failing test fix agentCI Fixer reproduces a failing test command in a public repository and returns the smallest change to the project's code that makes it pass, with the passing output.
ContextStream Agents are specialist context agents for Claude Code, Codex, Cursor and other MCP clients. Each is purpose-built and tuned to do one job very well, has to meet a quality bar in its own tests, and works from your workspace's own context: its code index, decisions, lessons and plans. Your coding agent hands one a job and gets back a short, structured result.
Each agent gets only the access its job needs, a workspace owner or admin turns it on, and it declines any task outside its job. Agents that run code do it in an isolated sandbox with no credentials inside.
15 agents in ContextStream today. Updated
Each agent is a program built and tuned for a single job, on general-purpose models reached through ContextStream's model proxy. Its own tests set a quality bar it must meet, including declining every task outside its job: 448 test cases with known answers across the 15 agents.
An agent reads what its job needs from your ContextStream workspace: the code index, decisions, lessons, plans, docs or connected repositories, plus the context ContextStream picks for its job. It works on your project as it is, not on a guess.
A run gets a short-lived token for one workspace, limited to the scopes its job needs, and writes nothing beyond them. A workspace owner or admin turns each agent on. Agents that run code do it in an isolated sandbox with no credentials inside.
Each page says what the agent does and declines, what it can access, how it is tested and how to call it, and shows a real run with its input, output and time.
CI Fixer reproduces a failing test command in a public repository and returns the smallest change to the project's code that makes it pass, with the passing output.
Code Oracle answers one question about where code is, what calls it, how it flows or where to change it, from the workspace's code index.
Data Analyst answers questions about one CSV or Excel table, in plain English or structured, with charts, and recomputes every number a second way before it reports it.
Dependency Upgrader upgrades a public GitHub repository within its semver ranges, fixes the project's code when that breaks its tests, and returns the diff and the results.
Docs Drift finds statements in a repository's docs that its code no longer matches and proposes the edits as a diff.
Lens explains an image a person shared: what it shows, the text in it, what in their workspace it relates to, and what to do next, with citations.
Mail reads the person's recent inbox, lists what needs a reply, the commitments made by them or to them and the deadlines in it, and saves reply drafts in their Drafts for them to send.
The Memory Gardener finds duplicate or conflicting decisions and lessons and stale open items, and proposes merging, superseding or closing them.
PDF lays out a source the person names (a doc, a plan, notes or markdown) as a PDF and stores it in the workspace.
Plans & Tasks Keeper answers one question about the status of the workspace's plans and tasks, citing their ids.
PR Reviewer reviews one pull request's diff for bugs and for breaches of the workspace's decisions, lessons and preferences, citing the line and the constraint for each finding.
Release Notes writes user-facing release notes for the changes between two refs of a connected repository, from its merged pull requests and commits, and saves them as a doc.
Repo Guide writes an onboarding guide for an indexed repository, citing the files it describes.
Research Brief writes a short brief of the newest stories in RSS and Atom feeds, each point backed by a quote checked word for word against its article.
Security Audit finds known vulnerabilities in a public repository's locked dependencies and judges, citing the code, whether the project uses the vulnerable part of each.
curl -fsSL https://contextstream.io/scripts/mcp.sh | bashOr install csa, with ContextStream's command line:curl -fsSL https://contextstream.io/cs/install.sh | shContextStream Agents are specialist context agents for Claude Code, Codex, Cursor and other MCP clients. Each is purpose-built and tuned to do one job very well, has to meet a quality bar in its own tests, and works from your workspace's own context: its code index, decisions, lessons and plans. Your coding agent hands one a job and gets back a short, structured result. Each agent gets only the access its job needs, a workspace owner or admin turns it on, and it declines any task outside its job. Agents that run code do it in an isolated sandbox with no credentials inside.
A general coding agent tries whatever you ask. A ContextStream agent does one job: it is built and tuned for that job, tested against a quality bar for it, grounded in your workspace's context, and limited to the access that job needs. It declines anything else. Your coding agent stays in charge and hands it the job.
No. Each agent is a program that calls general-purpose models through ContextStream's model proxy, with prompts tuned against its own tests. Your workspace's context is read for the run that needs it and is not used to train models.
Each agent has its own test suite of cases with known right answers: realistic jobs, inputs it must refuse with a clear error, and requests outside its job it must decline. A case passes only if the run ends the way the case expects and every check on it holds, such as every fact exact, every quote found in its source or every cited line real. Most suites run on fixed test data with a stand-in for the model, which checks everything ContextStream builds around the model rather than the live model's own answers; Code Oracle's replays recorded runs of the live model. Each agent's page says what its cases are and what they check.
Each agent's page lists exactly what it can access. A run gets a short-lived token for one workspace, limited to the scopes its job needs; it works in one project, only for that run, and declines any task outside its job. 7 of the 15 agents are read-only, and the rest can write only what their scopes name, such as one note or one doc per run. Agents that run code do it in an isolated sandbox with no credentials inside. A workspace owner or admin turns each one on.
All 15. ContextStream's MCP gives Claude Code, Codex, Cursor and other MCP clients an agents tool that finds an agent, runs it and follows the run, and csa run <agent> does the same from a terminal or an agent's shell.
Yes: Code Oracle. Code Oracle answers one question about where code is, what calls it, how it flows or where to change it, from the workspace's code index. More about Code Oracle
Yes: PR Reviewer. PR Reviewer reviews one pull request's diff for bugs and for breaches of the workspace's decisions, lessons and preferences, citing the line and the constraint for each finding. More about PR Reviewer
Yes: Release Notes. Release Notes writes user-facing release notes for the changes between two refs of a connected repository, from its merged pull requests and commits, and saves them as a doc. More about Release Notes
Each agent has a price per run in ContextStream credits. A priced run starts only once its price is accepted, and is charged only when it succeeds; a declined, failed, cancelled or timed-out run costs nothing. Code Oracle and Plans & Tasks Keeper are free. The others cost 400 to 8,000 credits a run. Credits come with every plan; Starter is free with 10,000 a month.
An owner or admin of your ContextStream workspace turns each agent on in the web app's agent library. Agents are opening workspace by workspace; if yours is not open yet, the library says so.