Documentation

npm install -g tokensmoker
smoke activate --email you@example.com
smoke status
smoke code "paste or type your prompt here"

This is the full path from install to a compiled prompt: install globally, activate with your account email, confirm status, then run an interactive compile.

smoke activate --email you@example.com

The CLI looks up your TokenSmoker account by email, negotiates credentials over TLS, and stores them locally. Activation is keyless: there are no API keys to copy, paste, rotate, or check into source control.

~/.tokensmoker/activation.json

• Credentials are machine-local — treat that directory like other developer secrets.
• Re-run activate if you reinstall or move machines.
• After you complete payment with smoke upgrade, run smoke status. Your local activation refreshes automatically — you do not need to rerun activate.

TokenSmoker routes prompts to harness-specific compilers. Each harness preserves the structure and constraints that matter for that kind of work.

TS-Code

Geared toward deterministic code and refactor workflows: stack traces, file paths, migrations, invariants, and the concrete engineering ask stay intact so the model can ship a strong first pass.

TS-Design

Optimized for UI and component prompts — ownership topology, Tailwind classes, quoted copy, assets, and motion hints compile into a brief that still reads like your design system.

TS-Docs

Preservation-first documentation compilation: audience, exclusions, tone, deliverable shape, and author intent are first-class. Token count may go down, stay flat, or grow when preservation is right.

TS-Docs requires explicit selection — use the docs subcommands or flags below; auto-detection will not silently route general text into the docs harness.

smoke "short inline ask"
smoke code "refactor the auth middleware…"
smoke design --paste
smoke design --file prompt.txt
smoke docs --paste
smoke docs --file prompt.txt

Auto-detection picks a harness from signal in the prompt when you use the generic entry (e.g. smoke "…"): code-like structure biases toward TS-Code; design-heavy prompts toward TS-Design. When in doubt, use an explicit subcommand.

smoke code --paste
# paste your prompt, then a blank line, then press Ctrl+D (Unix)
# or Ctrl+Z then Enter on Windows

• Blank line + Ctrl+D (or platform equivalent) commits the buffer cleanly.
• Recommended for long prompts so shell quoting, escaping, and argv limits never mangle your text.
• Pair with --file path when the prompt already lives in a file.

Below is a simplified before/after: a verbose prompt sharpened into a brief that keeps hard constraints explicit.

We're refactoring the checkout Service in services/checkout/index.ts. Please read the whole repo context, especially billing, the API routes under app/api/checkout, and the Prisma schema. Don't remove the idempotency-key header handling or the webhook signature verification. The PM also asked for clearer error messages but we can't break the existing JSON shape that older clients parse.

Task: refactor checkout Service (services/checkout/index.ts).

Preserve:
· Idempotency-Key handling
· Webhook signature verification  
· Existing JSON error contract / fields

Goal: clearer error messages without breaking older clients.

Context: billing module, app/api/checkout, Prisma schema.

• Constraints stay load-bearing — exclusions, invariants, and “do not change” rules remain visible instead of drowning in prose.
• Less ambiguity — the model sees what to do, what to protect, and where to look, which cuts rewrite loops.
• Stronger first-pass output — a tight brief beats a giant context dump for most coding agents.
• Preservation-first philosophy — shrinking tokens is not always the goal; sometimes the right compile is similar size or slightly larger when fidelity matters.

TokenSmoker subscriptions are handled securely through Stripe.

smoke upgrade

The trial is global per user, not per project. smoke upgrade is idempotent: if you are already on a paid plan, it does not create another Checkout session or charge you again. After payment, run smoke status — your local activation refreshes automatically; you do not need to rerun smoke activate.

smoke cancel

From the portal you can update payment details, switch plans, or cancel your subscription. smoke cancel does not cancel directly from the CLI — every billing change happens on Stripe's hosted page, where you can confirm or back out.

Canceling stops future billing cycles. Access remains active through the current billing period.

Can't use the portal? Use the billing link from your Stripe receipt or subscription email, or contact support@tokensmoker.ai.

TOKENSMOKER_API_URL=https://api.example.com

Override the API base URL for development, staging, or self-hosted backends. Most users should leave this unset and use the default production endpoint packaged with the CLI.

Harness availability at a glance: