# Common workflows (https://docs.ctxpipe.ai/docs/getting-started/common-workflows)

Each workflow starts from the same Workspace. People use
[Workspace chat](/docs/workspaces/chat). Coding agents use the
[MCP tools](/docs/mcp/use-from-your-agent).

## Plan a change across repositories

Link the repositories that a team owns to its Workspace. Before an agent plans
a change, it searches the knowledge for the decisions and standards that apply,
then searches the code in each linked repository. The
[knowledge graph](/docs/workspaces/graph) shows which services, APIs, and
libraries the change touches.

```text
Use ctxpipe before you plan this change. Find the decisions and standards that
apply, and the code in other repositories that calls this API.
```

## Give every agent the same instructions

Keep `AGENTS.md`, skills, ADRs, and contribution guides in linked repositories
or in the Workspace repository. ctxpipe returns them with the code that they
govern. Claude Code, Cursor, Codex, and your review bots then follow the same
guidance as your engineers. One MCP endpoint serves each client, so you do not
build retrieval for each agent.

## Bring product and incident context into git

Linear, Notion, Confluence, PagerDuty, Buildkite, and Plain mirror the scope
that you approve into the Workspace. Slack captures a thread when someone mentions the bot. The
result is Markdown with a git history, not a hidden index. An agent can cite
the issue or the incident behind a decision. See
[Connections](/docs/connections).

## Write it down once

When chat or an agent finds a fact that the team needs later, ask Workspace
chat to write it as a knowledge file. Review the diff and open a pull request. The next
person and the next agent start from that file.
[Local memory](/docs/mcp/local-memory) does the same for the lessons that
agents learn in one repository.

## Run headless agents and review bots

CI jobs, review bots, and other agents that cannot sign in through a browser
use an organization API key. See [API keys](/docs/mcp/api-keys).

## Run ctxpipe on your own infrastructure

The open-source core runs on Docker Compose, Terraform, or AWS CDK. Your source
data and model calls stay in your infrastructure. See
[Self-hosting](/docs/self-hosting).

<Cards>
  <Card title="Hosted quickstart" href="/docs/getting-started/quickstart" description="Create your first Workspace." />

  <Card title="Connect your agent" href="/docs/mcp/mcp-docs" description="Install the ctxpipe MCP." />
</Cards>
