# Getting started with ctxpipe (https://docs.ctxpipe.ai/docs/getting-started)

ctxpipe is context management for software factories. A software factory is the
set of coding agents, and the harnesses that run them, that a team uses to
write software.

Your coding agents can reach every repository, ticket, doc, and Slack thread.
They cannot tell which parts are true. ctxpipe gives them one organized,
current, and inspectable source of context: a git repository of Markdown that
you own, and that you can read, review, and correct.

1. **Connect.** [Link your code repositories](/docs/workspaces/linked-repositories),
   and [select what to bring in](/docs/connections) from Linear, Notion,
   Confluence, PagerDuty, Buildkite, Plain, and Slack. ctxpipe writes it as
   Markdown into one git repository for each [Workspace](/docs/workspaces).
2. **Keep current.** Background jobs mirror changes from your tools, and read a
   linked repository again after each push. Each job makes
   [one small commit](/docs/workspaces#what-ctxpipe-writes) that you can review
   or revert. Then ctxpipe
   [indexes the new commit](/docs/workspaces/indexing) for search and the graph.
3. **Serve.** Claude Code, Cursor, Codex, OpenCode, and VS Code read the same
   Workspace [through one MCP endpoint](/docs/mcp/mcp-docs). ctxpipe returns
   sources, not answers. Your agent reasons with its own model.

<ImageSlot title="ctxpipe Workspaces" src="/ctxpipe-workspaces-launch.gif" alt="ctxpipe Workspaces: chat, files, and graph" />

## Who ctxpipe is for

ctxpipe is for engineering teams that run coding agents across many teams and
repositories, and for the platform engineers who build the agent harness. It
helps when:

* agents repeat mistakes that a decision record or a runbook already explains;
* the context for one change is in several repositories and tools;
* you must see what an agent read, and correct it in one place.

For the full problem, the teams that ctxpipe is not for, and how ctxpipe
compares with other approaches, see [ctxpipe.ai](https://www.ctxpipe.ai).

## Key terms

| Term                     | Meaning                                                                             |
| ------------------------ | ----------------------------------------------------------------------------------- |
| **Organization**         | Your team in ctxpipe. It holds members, connections, and Workspaces.                |
| **Workspace**            | One body of knowledge, for example one product or one team.                         |
| **Workspace repository** | The git repository of Markdown that holds the knowledge of a Workspace. You own it. |
| **Linked repository**    | A code repository that a Workspace indexes for search.                              |
| **Connection**           | The authorization for one tool, such as Linear or Notion.                           |
| **Source**               | A file in the Workspace repository that says what to read through a connection.     |

## Choose your setup

<Cards>
  <Card title="Hosted ctxpipe" href="/docs/getting-started/quickstart" description="Sign up, connect GitHub, create a Workspace, and connect your agent." />

  <Card title="Self-host ctxpipe" href="/docs/self-hosting" description="Run the open-source core on your own infrastructure." />
</Cards>

## Give these docs to your agent

Point your coding agent at
[docs.ctxpipe.ai/llms.txt](https://docs.ctxpipe.ai/llms.txt). It lists each
page as Markdown. For all the pages in one file, use
[llms-full.txt](https://docs.ctxpipe.ai/llms-full.txt). To give the agent one
page, choose **Copy Markdown** under the title of that page.

## Learn more

<Cards>
  <Card title="Common workflows" href="/docs/getting-started/common-workflows" description="Where a shared Workspace helps engineers and agents." />

  <Card title="Workspaces" href="/docs/workspaces" description="The unit of knowledge in ctxpipe." />

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