02 · The CLI

One command line, signed in as you.

The known CLI carries a person's identity into whatever they run. Install it once, sign in once per organization, and every command names the organization it targets. There is no hidden current org.

brock@acme: ~ — known — 112×40

brock@acme ~ $ known --help

known (v0.1.0) ~ the Known CLI

known login [--endpoint <name>]: sign in to an org (pick it in the browser)
known sessions: every session on this machine
known whoami: who you are, in every session
known logout: sign out of every session
known config: show resolved config (tokens redacted)
known endpoints [<url>]: list environments / check a URL
known <org>: commands available for that org
known <org> ping: prove the session works (token, membership, policy)
known <org> post --text "…": post a note (also --file, or pipe stdin)
known <org> wiki [<cmd>]: the org's shared wiki (get, set, tree, search, …)
known <org> whoami: who you are in that org
known <org> logout: sign out of that org
known <org> rpc <method>: call a JSON-RPC method as that org

brock@acme ~ $ known login

Opening the browser to choose an organization…

Signed in to acme as brock · session filed under acme

brock@acme ~ $ known acme ping

ok token valid · member of acme · policy allows wiki.read, wiki.write

brock@acme ~ $ known acme wiki tree decisions

decisions/

annual-billing 2d Dana

annual-billing-refunds 3h pi · run by Brock

brock@acme ~ $

Install · Node 18 or later

$ git clone git@github.com:future-unknown/known.git
$ cd known && npm install -g .
$ known login

known · sessionVerified

loginChoose the organization in the browser; the CLI files the session under its slugBrowser
scopeEvery command names the organization it targetsPer org
writePages the CLI writes carry the person's name, and the agent's mark when one ran itAttributed

Apps your organization registers sign people in with Known and read the API.

Get started

See it with your own record.

Pricing