CLI + LOCAL WEBUI · AVAILABLE NOW

Project memory,
from the command line.

Initialize the repository once. Then tasks, docs, decisions, and agent context stay connected—in the terminal or the same local WebUI.

Install KnownsCLI reference
Local-firstNo hosted accountHuman + agent output
claude · ~/projects/atlas
Claude Code v2.1.206
Welcome back dev!
Opus 5 · Claude Max
knowns.dev
~/projects/atlas
Tips for getting started
Ask what the project already decided
What's new
knowns mcp connected · 247 files indexed
3 accepted decisions, 12 docs available
/release-notes for more
Project memory is stale · run knowns doctor
Work on the auth feature
Reading project memory before touching the code.
  1. Retrieve the decision behind auth (in progress)
  2. Create the task with its sources (pending)
  3. Start tracking the work (pending)
knowns search("auth" --type doc)3 sources · spec, decision, pattern
knowns doc("decisions/DEC-014" --plain)read 42 lines · accepted · 3 references
knowns retrieve("auth decisions" --limit 2)context pack · 2 citations attached
  1. Retrieve the decision behind auth (completed)
  2. Create the task with its sources (in progress)
  3. Start tracking the work (pending)
DEC-014 keeps tokens stateless — planning against it.
knowns task create("Add JWT auth" --ref @doc/DEC-014)TASK-042 created · 3 docs linked
  1. Retrieve the decision behind auth (completed)
  2. Create the task with its sources (completed)
  3. Start tracking the work (in progress)
knowns time(start TASK-042)Timer running · 00:00:04
  1. Retrieve the decision behind auth (completed)
  2. Create the task with its sources (completed)
  3. Start tracking the work (completed)
Context, plan, and timer now live in the repository.
plan mode on (shift+tab to cycle) · ← for agents
Same project state. Two surfaces.CLI ↔ LOCAL WEBUI
Knowns local WebUI showing the same task and project context created from the CLI.
TASK-042CONTEXT LINKED
Knowns knowledge graph showing links between tasks, docs, and decisions.
Works where your project already lives
TerminalClaude CodeCodexGitHub ActionsLocal WebUI

Commands become durable project state.

Knowns does more than print output. Every useful action leaves structured context that people and agents can inspect later.

knowns init

Create the memory layer

Repository structure, guidance, and the local index are prepared together.

knowns task create

Turn work into an addressable object

Priority, relationships, and source context travel with the task.

knowns retrieve

Recover the right context

Results include citations and lifecycle state instead of an ungrounded guess.

knowns doctor

Know what needs attention

Broken references and stale guidance surface before work starts.

THE RESULT IS REVIEWABLE

Knowns documentation view showing repository-owned project knowledge.
TASK-042 · Ship onboarding flowVERIFIED

sources  5    links  7    stale  0

next     knowns task TASK-042 --plain

5sources
4verified
0stale
7relationships

Retrieve the context that matters.

Find sources, assemble a cited context pack, and expand relationships only when you need them.

claude · knowns mcp · local index
What did we decide about onboarding? Then start the task.
Reading the project memory before touching anything.
  1. Search project sources (completed)
  2. Retrieve a cited context pack (completed)
  3. Create the task and start the timer (in progress)
knowns search("onboarding decisions" --type doc)2 sources · 1 decision, 1 spec
knowns doc("decisions/DEC-018" --plain)read 38 lines · accepted · 0 superseded
knowns retrieve("onboarding decisions" --keyword --limit 2)context pack · 2 citations attached(ctrl+o to expand)

CANDIDATES

13.533DECISION

Separate Spec Decisions from System Decisions

DEC-018 · accepted

5.380DOC

Decision Taxonomy Workflow Enforcement

specs/decision-taxonomy-workflow-enforcement

CONTEXT PACK

01 · Workflow rules for decisions and acceptance criteria

Citation: specs/decision-taxonomy-workflow-enforcement

02 · Current accepted system decision

Citation: DEC-018 · accepted

DEC-018 is the accepted decision — spec decisions stay separate. Creating the task against it.
knowns task create("Ship onboarding flow" --ref @doc/DEC-018)TASK-042 created · 1 relationship linked
knowns time(start TASK-042)Timer running · 00:04:12
TASK-042 now carries the decision, the sources, and the timer — anyone can reopen the same context later.
2 sources · citations attachedevery line inspectable

SEARCH

knowns search

Discover relevant sources before opening the full context.

RETRIEVE

knowns retrieve

Receive a ranked context pack with citations attached.

EXPAND

--expand-references

Follow relationships when the workflow needs more depth.

CANDIDATESranked source records
PACKsource-backed content
CITATIONtype + path or ID
MODEkeyword / semantic / hybrid
KNOWNS DESKTOP · COMING SOON

Project memory, now in a desktop app.

Launch Knowns from anywhere, switch between projects, and keep tasks, docs, decisions, and agent context in one local workspace.

Join early accessFollow development

Local-first · The CLI stays fully supported

Knowns Desktop dashboard showing tasks, project health, knowledge coverage, and recent activity.
DESKTOP PREVIEW
Knowns Desktop project switcher showing saved local workspaces.

Launch anywhere

Open Knowns without starting inside a repository.

Switch projects

Move between saved workspaces without restarting.

One local state

CLI, Local WebUI, and desktop share the same project memory.

From install to working context in three steps.

No hosted setup and no project migration. Start inside the repository you already have.

01

Install Knowns

Choose Homebrew, npm, shell, PowerShell, or npx.

❯brew install knowns-dev/tap/knowns
02

Initialize the repository

Knowns creates the local memory layer and project guidance.

❯knowns init
03

Choose your working surface

Stay in the terminal or open the same project in the local WebUI.

❯knowns browser --open
Your first task, doc, or search can happen immediately after init.Read the quick start

Install it your way.

Homebrew is the fastest path on macOS. npm, shell, PowerShell, and npx are available when they fit your environment better.

macOS, Linux, and Windows

No hosted account required

Verify with knowns doctor

Read installation notes

Recommended · Homebrew

Install the current Knowns CLI, then verify it before initializing a repository.

❯brew install knowns-dev/tap/knowns
knowns doctorready

Upgrade later with brew upgrade knowns.

Connect your coding agents

Pick a target, then generate the right repository guidance with one command.

repository guidance
❯knowns setup codex --global

Give your repository a memory.

Install the CLI, run knowns init, and keep every agent grounded in the same project context.

Install Knowns