Skip to content
PoketProject
Log inGet started
Early access · Built for Claude Code

The living map of your software project.

Your AI coding agent writes it. Your whole team understands it. It updates every time the code changes. Features, flows, APIs, data, integrations, environments, credential references, rules and decisions are drawn as animated maps and served to AI agents through MCP.

Get started free See how it works

Free during early access. Your code never leaves your machine.

Billingfeature · livePurchase flowflow · 12 stepsPOST /billing/checkoutendpoint · apiStripeintegrationsubscriptionsdata · postgresMoney in centsrule · must
Who writes itA developer, “later”. So, never.The coding agent, at the moment it changes the code
What it looks likeLong pages of textTyped objects, drawn as maps and animated flows
Who reads itPeople onlyPeople in a visual app, and AI agents through MCP
Our edge

When Claude changes your code, it knows why, because you just told it. Tools that read the code afterwards can describe what the code does, but not why. PoketProject saves the why at the moment of change, before it gets lost.

The problem

Documentation dies the day you write it

01

Code moves faster than docs

AI agents ship changes every day. Documentation written once is out of date within weeks.

02

Knowledge is scattered

It lives in code, in senior developers' heads, in chat, tickets, old PDFs and .env files.

03

Text is hard to read

People understand systems through flows and pictures, not through 40 pages of prose.

04

Agents start blind

Every session, the agent rediscovers the project, breaks conventions and repeats old mistakes.

How it works

One loop keeps knowledge and code in step

Documentation stops being a separate job. It happens inside the loop your team already uses to ship code with Claude Code.

The PoketProject loop: you ask Claude Code, Claude reads project context, Claude changes the code, Claude updates the knowledge, you review one pull request, and maps and agents refresh. Then the loop starts again.You ask Claude Codeplain-language taskClaude reads contextpoket_context_for_taskClaude changes codeknows how + whyClaude updates knowledgepoket_update + whyYou review one PRcode + .poket/ diffMaps + agents refreshnew truth everywhere
STEP 1 OF 6

You ask Claude Code

You describe a task in plain words, as usual. A PoketProject hook has already given Claude a short project brief and the team's rules.

A skill teaches how

Claude learns to write good knowledge: the right object type, short text, and always the reason behind a change.

A hook enforces when

If Claude changed code linked to knowledge, it can't finish until it updates that knowledge or explains why nothing changed.

CI catches the rest

Code written by hand or by other tools gets a check on every pull request that lists the knowledge that may be stale.

See it

A feature flow, the PoketProject way

This is a real flow from our reference example. Press play, follow either payment outcome and click any step. Then switch on Claude's proposed change to see what an update looks like.

Path
Memberactor.memberWeb appcomponent.webAPIcomponent.apiStripeintegration.stripePostgrescomponent.postgresSendGridintegration.sendgrid1Clicks "Subscribe" on the Pro plan2POST /billing/checkout {planId}3Check the plan and any existing subscription4Create a Checkout Session5Shows the hosted payment page6Payment OK?7Webhook: checkout.session.completed8Save the subscription and the payment in one transaction9Send the welcome email10Dashboard shows Pro as active
Trigger

Clicks "Subscribe" on the Pro plan

From → to
Member → Web app
Code
web/src/pages/plans.tsx#PlanCard

Dashed arrows run in the background. The flow is drawn from flow.purchase-subscription in the reference example.

What it stores

Structure first, text second

PoketProject doesn't store pages. It stores small typed objects and the links between them, as YAML files in a .poket/ folder next to your code. Maps, flows, search and agent context are all generated from them.

componentThings that run: web app, API, workers, databases
featureWhat users can do, with owners and business rules
flowStep-by-step scenarios, drawn as animated flows
endpointAPI endpoints with auth, errors and data use
dataTables and collections, fields and relations
integrationOutside services and their modes per environment
envLocal, staging and production: what runs where
secretWhere each secret lives and who owns it, never the value
ruleRules that agents and people must follow
decisionWhy things are built the way they are
incidentWhat went wrong, and what agents must watch out for
actor · team · personWho uses the product and who owns each part
# lives in your repo, next to the code
.poket/
├── project.yaml
├── components/   # web.yaml, api.yaml
├── features/     # billing.yaml
├── flows/        # purchase-subscription.yaml
├── endpoints/    # post-billing-checkout.yaml
├── data/         # subscriptions.yaml
├── integrations/ # stripe.yaml
├── environments/ # local, staging, production
├── secrets/      # references only
├── rules/        # what agents must follow
├── decisions/    # why, in Markdown
└── incidents/    # what to watch out for

Built for AI agents

Your agent reads it before coding, and updates it after

Connect Claude Code, Cursor, VS Code, Codex or Windsurf today through remote MCP with an access key. The Claude Code plugin, with hooks and commands, is coming.

MCP serverpoket

Read and write tools over .poket/. Every write is validated and scanned for secrets.

Skillpoket-knowledge

Teaches Claude to document well: short, typed, and always with the reason.

HooksSessionStart · Stop

Adds the project brief at the start, and blocks finishing while linked knowledge is stale.

Commands/poket:init · sync · explain

Map a repo in minutes, reconcile a branch, or explain any part of the system.

Subagentpoket-mapper

Runs big mapping jobs in its own context, so your session stays clean.

Connect Live now

Create an access key on a project's AI agents tab. The key stays in an environment variable, never in your repo.

# Claude Code, through remote MCP
claude mcp add --transport http poket https://<your site>/api/mcp \
  --header "Authorization: Bearer ${POKET_API_KEY}"

Claude Code plugin Coming

Hooks, the skill, commands and the subagent in one install. These commands will work once it's released.

# Claude Code: everything in one plugin
/plugin marketplace add poketproject/claude-code
/plugin install poket@poketproject

MCP tools

  • poket_context_for_taskThe right slice of knowledge for a task, within a token budget
  • poket_impactWhat a change to a file or object would affect
  • poket_search · poket_getFind objects and read them with their neighbours
  • poket_updateCreate or change objects in one validated changeset, with a why
  • poket_checkSchema errors and stale knowledge for the current diff

Security and trust

Credentials: store where, never what

# .poket/secrets/stripe-api-key.yaml
id: secret.stripe-api-key
env_var: STRIPE_SECRET_KEY
used_by: [component.api]
environments: [env.staging, env.production]
stored_in: op://Engineering/Stripe/secret-key
           # a vault reference, never the value
owner: team.payments
rotate_every: 90d

References, not values

Store where a secret lives, who owns it and how to get access. The value stays in your vault.

Secret scan on every write

Known key formats and random-looking strings are rejected before they reach Git.

People approve

Agents write drafts. Rules, decisions and secret references always need a person.

Code stays home

Your own agent writes the knowledge. PoketProject runs no model on your code.

Features

Everything your project knows, in one place

Live now: the web workspace, remote MCP, uploads, teams and repo sync. V1 adds the Claude Code plugin and PR checks, V2 adds more team features, and V3 adds enterprise features.

Understand

  • Project mapZoomable architecture with focus and filters
    MVP
  • Flow playerAnimated flows with branches, linked to code
    MVP
  • Feature, API and data pagesEverything about one part on one page
    MVP
  • Ask PoketProjectQuestions answered with real objects and diagrams
    V1
  • Guided toursAnimated onboarding for new developers
    V2

Keep it current

  • Agent write pathYour agent proposes docs; a person checks them
    MVP
  • Repo syncpoket push and pull, and a GitHub Action, keep the repo and the web copy in step
    MVP
  • Review inboxEvery draft with a before-and-after diff
    MVP
  • Activity and freshnessWhat changed, why, who, from which client
    MVP
  • PR comments and fixes“2 items may be out of date”, with a fix from Claude
    V1

Connect

  • Remote MCPHosted, with access keys, for every agent your team uses
    MVP
  • UploadsUpload a .poket folder or zip; download everything any time
    MVP
  • Local MCP serverWorks with any MCP agent, offline
    MVP
  • Claude Code pluginServer, skill, hooks, commands, subagent (coming)
    V1
  • OAuth for claude.ai and ChatGPTSign in from chat clients that cannot hold a key
    V1

Control

  • Secret referencesWhere secrets live, never the values
    MVP
  • Rules and decisionsGuardrails that agents follow; admins approve them
    MVP
  • Teams and rolesOwner, Admin, Member and free Viewers
    MVP
  • Vault connectionsCheck a secret exists without reading it
    V2
  • SSO and enterprise self-hostingFor enterprise security teams
    V3

FAQ

Questions people ask

Do I need Claude Code?

No. Any agent that speaks MCP, such as Claude Code, Cursor, VS Code, Codex or Windsurf, connects with an access key today. Claude Code will get the best experience once the plugin is out, because its hooks keep the docs up to date automatically.

Does my code leave my machine?

No. PoketProject runs no AI model on your code: your own coding agent writes the docs. The website stores only the .poket files you choose to sync, never your source code.

Where do secrets go?

Nowhere in PoketProject. It stores references: the variable name, where the value lives (such as a 1Password op:// reference), the owner and how to get access. Every write is scanned for secret values.

What if the AI writes something wrong?

Agents always write drafts, marked Needs review. A person checks each one on the Review tab with a before-and-after diff, and rules, decisions and secret references always need an admin.

Does it replace our wiki?

For how the system works, yes: features, flows, APIs, data, rules and decisions. Meeting notes and HR policies can stay where they are.

What does it cost?

Nothing during early access, and no credit card is needed. The free plan gives each workspace 2 projects, 3 editors and unlimited viewers, and each project 500 items, 5 access keys and 60 requests per minute per key. Viewers, access keys and agents are never seats. Prices for Team and Enterprise are set after the beta. Limits are not enforced during early access.

Can I try it now?

Yes. Create a free account, try the sample project, upload your .poket folder or connect your agent through remote MCP. Teams, roles and repo sync are live. The Claude Code plugin is coming.

Give your project a memory that keeps up with your code.

Create a free account, explore the sample project, and set up your first project in a minute.

Create your free account