Field Theory CLI

What does this agent do, and when should you use it?

Field Theory CLI is a local-first command-line tool for X bookmarks and a companion to the Field Theory Mac app. It stores bookmark data as JSONL, builds a SQLite FTS5 index, and provides search, filtering, statistics, visualization, and classification commands. It can export bookmarks to Markdown, compile an interlinked knowledge base, and answer questions against that knowledge base through `ft ask`. The CLI also manages local Library pages under `~/.fieldtheory/library` and portable commands under `~/.fieldtheory/commands`. Claude Code, Codex, and other agents with shell access can use the installed `/fieldtheory` skill to work with this local context.

With ft sync, the CLI reads session cookies from a supported browser's local cookie database when that browser is logged into X, then downloads bookmarks through X's internal GraphQL API. Alternatively, ft auth followed by ft sync --api uses OAuth API sync. It writes raw data to ~/.fieldtheory/bookmarks/bookmarks.jsonl and uses the SQLite FTS5 index in bookmarks.db for BM25-ranked ft search <query> results. ft classify and ft classify-domains classify bookmarks with an LLM; ft md exports per-bookmark Markdown; ft wiki compiles an interlinked knowledge base; and ft lint checks or fixes fixable wiki issues. The ft library commands search, create, SHA-256-protected update, trash, and open Library pages, while ft commands creates, lists, and validates portable commands.

1. An X power user wants a daily local bookmark sync and needs `ft search` to retrieve previously saved distributed-systems material.
2. A researcher wants to export bookmarked material as Markdown and use `ft wiki` plus `ft ask` to organize it into a searchable knowledge base.
3. A developer using Claude Code or Codex wants an agent to consult personal bookmarks and the local Field Theory Library while working on a task.
4. A Field Theory Mac app user needs to create or safely update Library pages from a terminal, then open them in the packaged app.
5. A user maintaining several local repositories wants to use `ft possible`, saved bookmark seeds, and a repository set to create opportunity prompts and background jobs.

What are this agent's strengths and limitations?

How do you install or deploy this agent?

Node.js 20+ is required. Install with:
npm install -g fieldtheory

For default session sync, use a supported Chrome-family browser or Firefox that is logged into X, then run:
ft sync

For cross-platform OAuth sync, run:
ft auth
ft sync --api

How do you use this agent?

Sync and search:
ft sync
ft search "distributed systems"

Explore the collection:
ft viz
ft categories
ft stats

Export and build a knowledge base:
ft md
ft wiki
ft ask "your question"

Check or fix fixable wiki issues:
ft lint

To make the local context available to Claude Code or Codex, run:
ft skill install

How does this agent compare with similar options?

FAQ