The CLI

The control panel

Run knwlge on its own in a terminal for a full-screen view of everything Knwlge does on your machine: which projects are connected, whether the sidecar and hooks work, and a live feed of every call.

Open it

shell
knwlge
knwlge — ~/code/acme
██   ▄█▀   Knwlge CLI v1.0.0   control panel
 █▄▄█▀     ● ada@acme.example · 2 projects
 █▀▀█▄     This folder: Acme Platform · api, web
██   ▀█▄   ~/code/acme
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Projects ──────────────────────────────────────────────────────────────────────────────────────────────────────────────
 ● Acme Platform   4 repos · 38 requests today · knwlge.acme.example  ◀ this folder
 ● Northwind Data  2 repos · 6 requests today · knwlge.northwind.example
 ● sidecar running · pid 48213 · 127.0.0.1:32770   hooks ● claude_code ● codex ○ copilot_cli ○ copilot_vscode ● cursor 

Activity · requests per day, last 14 days ─────────────────────────────────────────────────────────────────────────────
44                   ▄▄                   ██ 
                  ▂▂ ██ ▇▇    ▇▇       ▇▇ ██ 
   ▄▄ ▅▅ ▃▃       ██ ██ ██ ▆▆ ██       ██ ██ 
   ██ ██ ██       ██ ██ ██ ██ ██       ██ ██ 
   Sep 17                              today
   ■ Acme Platform 229   ■ Northwind Data 41   · claude_code 212 · cursor 64 · codex 31

Today · tokens are estimates: characters ÷ 4 ──────────────────────────────────────────────────────────────────────────
   44 requests · 19 briefs · 61 cards   23k tokens served · ~186k saved   5 knowledge writes · upkeep 48k tokens

Live · calls to Knwlge, knowledge written, and what you type ──────────────────────────────────────────────────────────

   15:12  ● Northwind Data  brief  2 cards · pipelines · cursor · 640 tokens · ~5.3k saved  “Nightly loads run in UTC; …
   15:21  ● Acme Platform  brief  4 cards · api, billing · claude_code · 1.8k tokens · ~14k saved  “Billing events are …
   15:22  ● Acme Platform  lookup  claude_code · 310 tokens  “InvoiceLedger”
   15:24  ● Acme Platform  search  claude_code · 950 tokens · ~6.1k saved  “retry policy for webhook deliveries”
   15:30  ● Acme Platform  entry described  claude_code  “InvoiceLedger”
   15:31  ● Acme Platform  memory saved  claude_code  “Never write billing_events directly”
   15:33  ● Acme Platform  asked the assistant to record  2 entries · claude_code
   15:36  ● Acme Platform  document edited  upkeep  “Billing — overview”
   15:37  ● Acme Platform  upkeep  done · 48k tokens
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
›  Type / for commands
ctrl+c exit · / commands · tab complete · ↑↓ history
The control panel with two projects connected, drawn by the CLI's own renderer from sample data.

It needs an interactive terminal; in a pipe or a script, knwlge status gives the same information as JSON. Every command still works on its own and exits as before.

What it shows

PartWhat it tells you
HeaderThe CLI's version, the account you are signed in as, how many projects are connected, and which project this folder uses.
ProjectsEach connected project with its repositories, today's requests and its server. ● is connected, ◐ signed in but its repositories could not be listed, ○ signed out. ◀ this folder marks the folder's project.
Sidecar and hooksWhether the service answers, its process and address, and each AI client's hook: ● installed and working, ◐ installed but not verified, ○ not installed.
ActivityRequests per day for the last 14 days, stacked by project in each project's fixed colour, with each project's total and the requests per AI client.
TodayRequests, briefs and cards; the tokens they served and the tokens they spared; what was written to the knowledge base; and what the background upkeep cost.
LiveOne stream, newest at the bottom, of what Knwlge does as it does it — and what you type at the prompt, with what it printed.

The live feed names each kind of event:

In the feedWhat happened
briefA prompt was briefed: its cards, repositories, client, tokens and first card's title.
search · lookupThe assistant called context.search or knowledge.lookup, with what it asked.
entry described · memory saved · document editedSomething was written to the knowledge base, in the Knwlge colour.
asked the assistant to recordThe learning nudge asked the assistant to save what it learned.
upkeepThe background upkeep ran, with its outcome and tokens; calls it made are marked upkeep.

Commands

Type / at the prompt for the commands. Tab completes, Enter runs, ↑ and ↓ walk the history, and Ctrl+C clears the prompt — pressed again on an empty prompt, it leaves the panel.

CommandWhat it does
/projectsThe connected projects and their repositories.
/which [dir]Which project a folder uses, and why.
/refreshRe-read every project's repositories and sessions now.
/init <server>Connect a project. The panel steps aside for the browser sign-in.
/logout <project> | --allSign out of a project, or of all of them.
/pin <project> [dir]Always use a project in a folder.
/unpin [dir]Match a folder by its repositories again.
/sidecar start | restart | statusInstall or start the background service, restart it (picks up a new build), or show its state.
/installWire AI clients; on its own, Claude Code in this folder.
/doctorCheck the install end to end.
/statusThe full status report.
/run <anything>Run any other knwlge command here.
/clear · /help · /exitClear the output, list the commands, leave the panel.

How tokens are estimated

Tokens in the panel are estimates made on your machine — characters divided by four, the same rule the Enterprise Server's Insights uses.

  • Served is the text that reached the assistant: a brief's context, a tool call's result.
  • Saved is the rest of each file a served excerpt came from, measured in your local checkout — what the assistant did not have to read. A file that is not checked out counts for nothing, and one file for at most 200,000 characters.
  • Upkeep is what your own client spent keeping the team's documents current.

The activity log

The charts and the feed come from a local log in ~/.team-context-gateway/activity/: 30 days, readable by you only. It keeps what each call was about — a brief's first titles, a memory's or document's title, a search's words. Only its counts are sent to Knwlge Global, every ten minutes, for your Dashboard at knwlge.com: never prompts, cards, titles, token estimates or repository names.