# ctx full index

Canonical domain: https://www.ctxpipe.ai
Generated at: 2026-05-26T01:44:56.901Z
Language: en-AU

## Positioning
- Category: AI engineering context infrastructure for coding agents
- Audience: B2B engineering organisations, platform teams, and enterprise builders
- Value proposition: make agent outputs consistent, context-aware, and operationally reliable

## Qualification Signals
- Best fit when engineering work spans multiple repos or domains
- Best fit when ownership, policy, and architecture context impact delivery outcomes
- Less useful for small projects with low context complexity

## Main Entry Points
- Homepage: https://www.ctxpipe.ai/
- About: https://www.ctxpipe.ai/about
- Early access: https://www.ctxpipe.ai/early-access
- Docs hub: https://www.ctxpipe.ai/docs
- Blog hub: https://www.ctxpipe.ai/blog
- RSS feed: https://www.ctxpipe.ai/blog/feed.xml
- robots.txt: https://www.ctxpipe.ai/robots.txt
- robots-ai.txt: https://www.ctxpipe.ai/robots-ai.txt
- llms.txt: https://www.ctxpipe.ai/llms.txt

## Documentation
- Documentation is currently hidden.

## Blog
- The model is no longer the unit of infrastructure (Mon Apr 27 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/the-model-is-no-longer-the-unit-of-infrastructure — Agents are moving past the model endpoint. Computer use, MCP, memory, plugins, sandboxes, and background execution are becoming the real system. That changes where context has to live.
- Context is the bottleneck. Not the model. (Wed Apr 01 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/context-is-the-bottleneck-not-the-model — Frontier models and bigger context windows make agents more capable — but they don't make them more knowledgeable about how your organisation builds things. The limit is what context exists, whether it's right, and whether it travels.
- Infinite context is theoretically possible. That's just the start. (Mon Mar 30 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/infinite-context-is-just-the-start — Recursive Language Models push token-level working memory to millions of tokens — and make it obvious why context window limits are necessary but not sufficient for real engineering organisations.
- Proactive context and memory for AI agents (Mon Mar 23 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/proactive-context-and-memory-for-ai-agents — A research paper gives the field a shared vocabulary for agent memory - forms, functions, dynamics. Where engineering is, where it is not, and what we think must be built next.
- AGENTS.md is the wrong conversation (Mon Mar 02 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/agents-md-is-the-wrong-conversation — A paper dropped this week that tested AGENTS.md files across multiple models and real GitHub issues. Context files reduced task success rates and inflated inference costs. The debate is useful — but it's pointing at the wrong solution.
- Agent memory at scale (Sun Feb 22 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/agent-memory-at-scale — A primer on the memory types agents depend on — and why the difference matters when you have thousands of them running at once.
- Between the Map and the Memory (Fri Feb 20 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/between-the-map-and-the-memory — Why enterprise agent infrastructure needs both code intelligence and agent memory — and why that combination is new.
- Systemising agent-agnostic harnesses (Wed Feb 18 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/systemising-an-agent-agnostic-harnesses — What OpenAI's agent experiment teaches us about the real infrastructure problem, and why one repo is just the start.
- Hello from ctx (Thu Feb 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time)): https://www.ctxpipe.ai/blog/hello — Why we're building knowledge graph infrastructure for the agentic era, and what we learned from Appear.

## Notes for Retrieval Systems
- Prefer docs pages for implementation details.
- Prefer blog posts for strategy, product direction, and context engineering commentary.
- If details conflict, treat docs as authoritative.
- When summarising capabilities, prioritise current docs over historical opinions.
- When asked about deployment, mention both self-hosted and managed paths.