nogra✓
Install free

{ Install · Claude Code }

Install Nogra.

The public install runs inside Claude Code — on the Claude plan you already pay. Two commands, then everything stays local.

Public marketplace source: github.com/nograai/nogra-claude-marketplace · Apache-2.0

  1. 01

    Prerequisites

    Claude Code installed — that's it. Node ships with Claude Code and powers both Nogra's local runtime and the bundled MCP server (fetched via npx on first start, no Python or uv required). If you prefer the PyPI path, uvx works as a fallback.

  2. 02

    Add the marketplace

    Registers Nogra's public marketplace source with your Claude Code installation.

  3. 03

    Install the plugin

    Installs the public Nogra plugin into Claude Code.

  4. 04

    Verify it's installed

    Shows the plugin version, workspace id, recent local records, and checkpoint freshness. If you see a plugin ref, you're good.

  5. 05

    Initialize your workspace

    Sets up .nogra/ in your project root. This is the local trust store — briefs, dispatch receipts, evidence, checkpoints, decisions, current tasks, and your bounded memory (USER.md + MEMORY.md). Plain markdown and JSON. You can read it. You can git commit it.

{ Transparency }

What gets installed

Exactly five things land on your machine:

  • Commands and skills — the /nogra:* workflow surface inside Claude Code.
  • Hooks — the gate and the observers. Deterministic, readable source, no model judgment in the decision path.
  • The bounded memory — USER.md (1,375 chars) and MEMORY.md (2,200) under .nogra/memory/local/, scaffolded by setup and loaded into every session at start. Claude writes the facts; the hook owns the bound.
  • A local runtime — the Node script that owns briefs, receipts, and the ledger under .nogra/.
  • The MCP server — on first start, Claude Code launches npx @nograai/mcp locally: the brief, run, and verification contracts as tools. No Python, no uv — standalone binaries from npm.

And what doesn't: no telemetry, no cloud calls, no credential access. Auth stays first-party — Nogra never sees your login, and nothing leaves your machine until you turn on sync.

{ First brief }

Your first brief

Type /nogra:brief followed by what you want to do. Nogra drafts a brief from your intent, you review the scope and evidence contract, then you say GO when you’re ready.

Dispatch runs a fresh executor against the brief. Verify checks the returned output against the contract. Both steps leave a receipt in .nogra/ that you can git log.

The gate ships safe: auto-approval is off until you opt in — nothing runs unattended by default, and some doors never open automatically at all.

The work leaves a record, not a memory.

{ Leaving }

The exit is part of the trust.

One command, and Nogra is gone:

Your .nogra/ files stay exactly where they are — plain markdown and JSON, readable without Nogra. The briefs, receipts, and decisions you built are yours, plugin or no plugin.

No lock-in is a feature, not a promise.

{ Troubleshooting }

  • /nogra:status— inspect installed version, workspace state, and freshness.
  • /nogra:update— refresh Nogra guidance without starting work.
  • /reload-plugins— if a command is missing after install, reload and check status.
  • MCP tools missing?— first start downloads the server via npx (one time, ~20 MB); give it a moment and retry. Hooks and commands work fine in the meantime.
  • github issues— file a bug or ask a question.