News

Project Wikis, Plans, Version History & More

This release is our biggest yet: AI-maintained Project Wikis, new Pro and Pro Plus plans, item version history, smarter hybrid search, and refreshed MCP and CLI tooling.

Project Wikis

Your projects can now generate their own AI-maintained wiki — a living knowledge layer built from your project's content. Kick off generation with one click (or via the API, CLI, or MCP server), then browse summaries, entities, concepts, and indexes that stay linked back to the exact sources they came from.

  • Browse and search wiki pages in the dashboard, with internal links between pages and combined full-text and semantic search
  • Ask questions — the wiki synthesizes grounded answers from your project's content, with citations back to your sources
  • Always in your control — generation only runs when you ask for it (or when you opt into auto mode), external-LLM use is an explicit per-project opt-in, and status indicators show when the wiki is fresh, stale, or generating
  • Built for big projects — a durable, resumable generation pipeline means even large corpora complete reliably

Project Wikis are available on the Pro and Pro Plus plans.

Subscription plans

We've launched Pro and Pro Plus plans alongside the free Standard tier, with in-app pricing, checkout, and plan management. Paid plans unlock Project Wikis and Version History, include a monthly AI usage allowance (largest on Pro Plus), and extend version retention. When a feature needs a higher plan, the upgrade prompt appears right where you are — no digging through settings.

Item version history

Every edit to an item now captures a version snapshot automatically. Browse an item's full history in the dashboard, see what changed, and restore any previous version with one click. Retention scales with your plan: 30 days on Standard, 90 days on Pro, and a full year on Pro Plus.

Search is now hybrid: keyword matching and semantic vector search work together, so you find things whether you remember the exact words or just the idea. A similarity floor filters out low-relevance noise, and results now show why they matched. You can also keep files with the same name in different folders of the same project.

MCP server & CLI 0.2.0

  • MCP 0.2.0 ships a unified eight-tool surface — search, fetch, browse, save, edit, delete, list_projects, and create_project — that's simpler for agents to discover and use, backed by a server that now scales horizontally
  • CLI 0.2.0 adds a ctx wiki command group for generating, checking, and querying Project Wikis from your terminal, plus clearer authentication state and honest error messages when credentials are wrong
  • Errors across the CLI, MCP server, and API are now actionable — rate limits, quotas, and permission problems tell you exactly what to fix

Nothing breaks

Existing API calls, CLI commands, and MCP operations keep working as before. Version snapshots are captured automatically with no setup, and the wiki is entirely opt-in — nothing is generated until you ask.

Folder Architecture

You can now organise items into folders — giving your projects a familiar, nested structure that grows with you.

What's new

Every project now supports folders, so you can group related items the same way you would on your own file system. Create a folder like prompts/onboarding, drop items into it, and browse or search within any level of the hierarchy.

  • Nest up to six levels deep — enough for most workflows without getting unwieldy
  • No setup required — folders are created automatically the first time you place an item in one
  • Works everywhere — the API, CLI, and MCP server all support folders from day one, with web UI browsing in the dashboard

How you might use it

  • Separate drafts from published content — e.g. docs/drafts and docs/published
  • Group prompts by purpose — e.g. prompts/system, prompts/user, prompts/few-shot
  • Mirror your repo layout — keep context items next to the code they relate to
  • Scope searches to a subtree — search only within guides/ instead of the whole project

Nothing breaks

All existing API calls, CLI commands, and MCP operations continue to work exactly as before. Items that aren't in a folder stay at the project root — no migration needed.

Get started

Place an item in a folder via the CLI, API, or MCP server and the folder appears automatically. Browse your folder tree in the dashboard or list folders through the API. That's it — no configuration, no extra steps.