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.
✓ Project initialized .knowns/
✓ Repository indexed 247 files
✓ Agent guidance ready AGENTS.md
Created TASK-042 · linked 3 docs · 2 source references
{ "sources": 5, "verified": 4, "stale": 0, "next": "TASK-042" }
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 initCreate the memory layer
Repository structure, guidance, and the local index are prepared together.
knowns task createTurn work into an addressable object
Priority, relationships, and source context travel with the task.
knowns retrieveRecover the right context
Results include citations and lifecycle state instead of an ungrounded guess.
knowns doctorKnow what needs attention
Broken references and stale guidance surface before work starts.
THE RESULT IS REVIEWABLE
sources 5 links 7 stale 0
next knowns task TASK-042 --plain
Retrieve the context that matters.
Find sources, assemble a cited context pack, and expand relationships only when you need them.
❯knowns retrieve "onboarding decisions" --keyword --limit 2
Found 2 ranked sources · keyword mode
CANDIDATES
Decision Taxonomy Workflow Enforcement
specs/decision-taxonomy-workflow-enforcement
Separate Spec Decisions from System Decisions
DEC-018 · accepted
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
SEARCH
knowns searchDiscover relevant sources before opening the full context.
RETRIEVE
knowns retrieveReceive a ranked context pack with citations attached.
EXPAND
--expand-referencesFollow relationships when the workflow needs more depth.
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.
Local-first · The CLI stays fully supported
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.
Install Knowns
Choose Homebrew, npm, shell, PowerShell, or npx.
Initialize the repository
Knowns creates the local memory layer and project guidance.
Choose your working surface
Stay in the terminal or open the same project in the local WebUI.
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 --version
Recommended · Homebrew
Install the current Knowns CLI, then verify it before initializing a repository.
❯brew install knowns-dev/tap/knownsknowns --versionreadyUpgrade later with brew upgrade knowns.
Connect your coding agents
Pick a target, then generate the right repository guidance with one command.
❯knowns setup codex --globalGive your repository a memory.
Install the CLI, run knowns init, and keep every agent grounded in the same project context.
Install Knowns