txt-cli

txt-cli

notes, plans, shared skills, and direct byok ai · v0.4.25 · zero CLI deps

# install

one-shot · no global install · same saved login as a later `txt`

✓ connected to txt-fil.es

existing dots sign-in approved · revocable device key kept locally

# try something01/20

catch a passing thought

A terminal thought appears instantly in your txt inbox.

ideas seeded with qwen3 · commands human-checked

# connected? try it here with your real notes

checking browser session…

wterm UI · real same-origin TXT actions · no shell, local disk, or exposed API key

# complete command index

grouped from the current txt-cli surface · detailed workflows continue below

## account & help

## notes & cloud folders

## AI & handwriting

## sync, daemon & device state

## plans, context & ideate

## group skills

## agents, connections, MCP & automation

click a command to copy · no $ prefix · -f = --folder · -w = --watch · -a = --action · -p = --prompt · -h = --help

# AI · off until you provide a key

provider and model are saved · the key is not · your CLI calls the provider directly

AI generates a new note · the filename and prompt both describe the result

overwriting always requires both explicit flags

txt-fil.es/ai — confirm provider in the browser

# mirror a folder onto disk

✓ pull shows.txt · pull sets.txt · pull run-of-show.txt

./notes/sync.txt holds the folder id — later runs need no flags

In sync (3 files).

two-way · local saves after 1 quiet second · web polling pauses while you type

explicitly rename the local directory to match its web folder

both sides changed? your file stays, the web copy lands beside it

keep and push the local copy · use --resolve web to keep the saved web copy

--folder root mirrors notes outside any folder · --json for scripts

# keep syncing with no terminal open

✓ mirroring in the background — restarted on failure and at login

launchd on macOS · systemd --user on Linux · one agent per folder

the agent reads your saved config — no API key is ever written into it

# session

✓ .plans/launch-plan.md linked

watching web ↔ local

# group skills [experimental]

shared SKILL.md trees, skills.sh install, and org folders · still moving

lists ~/.claude/skills and <repo>/.claude/skills instantly · no upload

look up the skills.sh catalog through txt · no repo required

writes notes into the shared .skills system folder · works from the web too

✓ publish claude/ship/SKILL.md · reveal https://txt.mn/skills

opt-in catalog · fans global skills into Claude and Codex homes

GET /api/v1/skills · includes notes shared with you

public folder link · grant writers as dots collaborators on the .skills folder

# connections · tools · MCP

txt is the durable note/file system · Executor supplies authenticated connector tools

shows the sidecar, daemon, and discovered integrations

checks Executor plus the txt tool registration without changing connections

✓ register the txt OpenAPI surface as tools

authenticate MCP/OpenAPI connectors in Executor · credentials stay there, never in skills

AUTOMATION.json lives beside SKILL.md · approval is local, hash-bound, and never synced

https://txt-fil.es/mcp — direct MCP endpoint · Bearer txt_ key from /sync

API + OpenAPI reference — files, folders, changes, webhooks, skills, transcription, and ideation

# ideate [experimental]

a note that writes itself from the context brain · tags, folder, connections

creates a markdown note · explores clusters, ghosts, and related files

another pass · the note deepens and reconnects itself

`txt ideation …` remains a full alias for scripts and muscle memory

GET /api/v1/ideation · same unlock as aclue (subscription or /ai key)

# security

plans are plaintext reference — never store secrets in them

$ npmjs.com/package/txt-cli

$ github.com/text-co/txt

$ txt-fil.es/sync — create an API key

$ txt-fil.es — open the editor

$