Skip to content

DocsCommands

FutureX CLI commands

Every command FutureX accepts, every flag it takes, and the files that configure it. One page, no hunting.

All documentation pages

Commands

One binary, one habit: read the repo first, then act. Run these from your project root. If the CLI is not installed yet, start with the quickstart — install, sign in, first change.

futurex help
# the same list, printed in your terminal

19 of 19 commands

Every FutureX CLI command and what it does
CommandWhat it does
futurexOpen the interactive REPL. No arguments, no ceremony.
futurex ask "<prompt>"One-shot answer, then exit.
futurex agent "<task>"Agentic loop: the model uses tools. Reads happen automatically, writes are gated.
futurex indexIndex the repo so answers can be retrieval-augmented.
futurex symbols [name]Query the AST symbol index.
futurex imports [file]Show the import graph, plus any broken imports.
futurex initCreate futurex-memory.md if it is not there yet.
futurex compactBound the size of futurex-memory.md: regenerate it, archive the old one.
futurex plan "<task>"Pre-build plan: goal, value and budget, research, tooling, and a task DAG.
futurex build "<task>"Plan, then execute against the plan.
futurex resumeResume the latest chat session. --list to see them, --session <id> to pick one.
futurex skills [request]List skills, or route a request to the skills that match it.
futurex permissionsPer-project consent: show, set <kind> <state>, or reset.
futurex verify [--list]Project diagnostics: typecheck, lint, test, build.
futurex testRun the project test script.
futurex loginSign in with a browser link code. --no-browser prints the code instead of opening a tab.
futurex logoutClear stored credentials.
futurex whoamiShow the current backend and auth mode.
futurex helpShow help.

init and compact both act on the project memory file — how that works is on project memory.

Options

Flags go after the command. Anything scoped to particular commands says so in its description.

futurex agent "add a health check" --tier fx-pro --max-steps 12
Every FutureX CLI flag and what it does
FlagWhat it does
--tier <module>Pick the module: fx-pro, fx-fast, fx-mini, or fx-eco.
--effort <level>off, high, or max — enforced against the module you picked.
-r, --reasonUse more reasoning effort (high).
--maxMaximum reasoning. Implies fx-pro.
--proUse the fx-pro module.
-m, --model <id>Override the underlying model id. Advanced.
--max-tokens <n>Cap output tokens.
--no-memoryIgnore futurex-memory.md for this run.
--no-repoDo not include the repo card.
--no-contextDo not augment the prompt with retrieved repo chunks.
--top-k <n>Chunks retrieved per turn. Default 6.
--auto-approveagent — run mutating tools without prompting. Dangerous; know why you typed it.
--jsonask, agent — JSONL events on stdout, exit 0 or 1.
--output-format <f>json or text. Alias of --json.
--max-steps <n>agent — max model and tool rounds. Default 32.
--no-verifyagent — skip the automatic typecheck, lint, and test after edits.
--value <tier>plan, build — low, standard, high, or critical.
--budget <n>plan, build — cap the build token budget.
--restartplan, build — ignore checkpoints and re-plan from scratch.
-v, --versionPrint the version.

The four modules — Pro, Fast, Light, and Eco — carry their own default effort and output cap. Which to reach for, and what each one costs, is on models.

Settings files

Two files, read in this order:

settings.json
~/.futurex/settings.json        # your machine
<repo>/.futurex/settings.json   # this project
Keys a FutureX settings.json file carries
KeyWhat it sets
permissions.allow / permissions.denyStanding consent rules — the same ground futurex permissions covers, written down.
hooksYour own commands, run as part of a FutureX run.
defaultTierThe module a run starts on when you do not pass --tier.
verifyHow the automatic checks behave after an edit. --no-verify skips them for one run.
mcpServersMCP servers the CLI connects to.

Permissions are per project on purpose: consent you gave one repository should never follow you into another one.

Environment

One variable. FX_API_KEY in a .env file is loaded automatically when you run futurex.

.env
FX_API_KEY=your_key_here

No key on hand? Run futurex login and sign in through the browser with a link code. Then futurex whoami tells you which backend and auth mode you landed on, and futurex logout clears it again.

Either way you are billed by usage: $1 per 1M tokens on Fast, $2 per 1M on Pro, with a free first month on new accounts. The full breakdown is on pricing.

futurex build "the thing you keep postponing"

Read the reference. Then run the thing.

Install the CLI, sign in once, and every command on this page works from any terminal. New accounts get a free first month — no card.

Node 20+ · Windows, macOS, Linux