dexterm-cli 0.1.6 → 0.2.0

package/dist/packages/mcp/assets/kb/docs/docs-going-real-what-dexterm-does-and-never-does.md

@@ -0,0 +1,44 @@
+---
+id: docs-going-real-what-dexterm-does-and-never-does
+title: Going real, safely › What dexterm does, and never does
+kind: docs
+page: going-real
+page_title: Going real, safely
+heading: What dexterm does, and never does
+anchor: what-dexterm-does-and-never-does
+url: https://dexterm.xyz/docs/going-real#what-dexterm-does-and-never-does
+tags:
+  - docs
+  - going-real
+  - dexterm
+  - does
+  - never
+  - going
+  - real
+  - safely
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/going-real.md
+date: 2026-10-16
+---
+
+**It does:**
+- run your strategy exactly like paper;
+- turn each trade into a signed, numbered, expiring signal for your executor, inside your limits;
+- keep the signal until it is delivered;
+- record what your executor reports;
+- pause new buys when your executor is silent or a loss limit trips;
+- tell you each time.
+
+**It never:**
+- holds, imports or asks for a key or a seed phrase;
+- signs or sends a transaction, or builds one;
+- lets a model, a tool or a chat tap arm real mode, change a limit, lift the kill switch or reset the breaker;
+- trades a test signal;
+- promises a fill or a profit.
+
+Your executor decides, at its own price, with its own fees.

package/dist/packages/mcp/assets/kb/docs/docs-going-real-your-limits.md

@@ -0,0 +1,77 @@
+---
+id: docs-going-real-your-limits
+title: Going real, safely › Your limits
+kind: docs
+page: going-real
+page_title: Going real, safely
+heading: Your limits
+anchor: your-limits
+url: https://dexterm.xyz/docs/going-real#your-limits
+tags:
+  - docs
+  - going-real
+  - limits
+  - going
+  - real
+  - safely
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/going-real.md
+date: 2026-10-16
+---
+
+Every number real mode enforces is yours. They live in one file, `~/.dexterm/autotrade/real/limits.json` (schema `dexterm-limits/1`; `dexterm autotrade limits schema` prints its JSON Schema), outside the model.
+
+**Sizing:**
+- `perTradeSol` and `perTradePct`: the most one buy may spend, in SOL or as a percent of the book. With both set, the smaller wins.
+- `dailySol` and `buysPerDay`: what all buys may spend, and how many there may be, per local day.
+- `maxOpenPositions`: counted across every real holding on this machine.
+- `maxExposurePct`: everything open together, as a percent of the book.
+- `minPositionSol` and `maxPositionSol`: no dust orders, and a cap on one position with its adds.
+- `perCoinSolPerDay` and `perCoinBuysPerDay`: how much one coin may take in a day, re-entries included.
+- `bookSol`: the size of YOUR account, which the percent limits use. Unset, they use the strategy's own book.
+
+**Risk:**
+- `dailyLossSol`: once the day's realized loss reaches it, no new buy goes out until tomorrow.
+- `maxDrawdownSol`: the drawdown breaker. It stops new buys until you reset it with `dexterm autotrade limits breaker reset` (typed). The reset also lifts a loss-streak pause and starts the streak count again.
+- `lossStreak` and `lossStreakPauseMin`: that many losing closes in a row pause new buys for that long.
+- `maxHoldMinutes`: the stricter of this and each exit profile's own cap.
+- `minLiquidityUsd` and `minMcapUsd`: floors on the coin. While one is set, an unknown value is refused.
+- `maxSlippageBps` and `maxPriceImpactPct`: the tolerance a signal states. A buy is cut to the price-impact cap on the pool.
+- `signalTtlSec`: how long your executor may act on a signal.
+- `maxBuysPerMinute`: the signal rate limit.
+
+**Sells:** never capped, unless you set `maxSellsPerMinute`. Only the kill switch stops exits.
+
+**Evidence:** `minForwardTrades`, the evidence floor for arming: the closed paper trades a completed forward test of the strategy's exact rules must have, with a backtest on record. Lowering it or turning it `off` (no trade minimum; the completed forward test and the backtest are still needed) is a raise.
+
+**Executor:** `executorSilenceMin`, how long your executor may be silent before new buys pause (see executor health (https://dexterm.xyz/docs/going-real#executor-health)).
+
+Loss limits are counted on dexterm's own fills: the paper view of every signal.
+
+**Scopes, and the stricter wins.**
+- A number in `global` replaces the placeholder default. `off` turns a global limit off, which is a raise.
+- `real` / `paper` (a mode), `strategy:<id>` and `account:<id>` can only tighten. Whichever scope sets the stricter number, that number is in force: a smaller cap, or a larger floor.
+- Paper runs ignore limits unless you add a `paper` scope. Then a single paper run (`dexterm autotrade run <id> --paper`, a forward test included) obeys them too, the way a real run would, on its own state (it never touches real mode's counters). Limits are in SOL, so a paper replay with a `paper` scope needs `--sol-usd N`. Running several strategies at once (`run --all --paper`) does not apply the paper scope yet.
+- The day's counters (buys, SOL spent, realized loss, per coin) count every real buy from this home: all strategies and accounts together. A `strategy:` or `account:` number is compared with that total, so it can only stop buys sooner, never later.
+
+```
+dexterm autotrade limits show --strategy my-strategy --account main   # what is in force, and where each number comes from
+dexterm autotrade limits set perTradeSol=0.5 dailySol=2 dailyLossSol=0.4
+dexterm autotrade limits set --scope strategy:my-strategy perTradePct=2 maxOpenPositions=1
+dexterm autotrade limits explain maxExposurePct
+```
+
+**Lowering is free and immediate.** A running real run re-reads the file and uses the stricter of what it started with and what the file says now.
+
+**Raising needs you.** `limits set` shows every change old -> new, marks each RAISE, and asks for a typed phrase with a one-time code on your own terminal. A pipe, a flag, an agent or MCP cannot give it. A raise applies from the next run.
+
+**Hand edits.** If you edit `limits.json` by hand, a real run accepts the edit only when it lowers. One that raises anything is refused until you review it (`dexterm autotrade limits diff`) and accept it (`dexterm autotrade limits accept`, typed). Everything is journaled. Caps you set before 0.2.0 (`caps.json`) carry over as your global numbers, unless they differ from what dexterm last saved: then they count as a hand edit too.
+
+**The placeholders** are 0.25 SOL a trade, 1 SOL a day, 20 buys a day, 3 open positions, a stop at -0.5 SOL a day, a pause after 5 losing closes in a row (60 min), at most 3 buys a minute, a pause when your executor is silent for 15 minutes, and an evidence floor of 10 closed paper trades. They are a cautious starting point, not advice. Real mode never arms on them silently: the first arming asks for your own numbers, and every arming shows the limits it confirms.
+
+**The analyst can explain, never apply.** Ask it "why was that buy refused?" or "what would a 1 SOL daily cap change?". It reads the limits (`trading_limits`) and can propose a change as a diff card (`limits_propose`) with the exact command for you to run. No tool, chat command or model decision can change a limit.

package/dist/packages/mcp/assets/kb/docs/docs-going-real.md

@@ -0,0 +1,24 @@
+---
+id: docs-going-real
+title: Going real, safely
+kind: docs
+page: going-real
+page_title: Going real, safely
+url: https://dexterm.xyz/docs/going-real
+tags:
+  - docs
+  - going-real
+  - going
+  - real
+  - safely
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/going-real.md
+date: 2026-10-16
+---
+
+The whole path from a paper strategy to real trades through your own executor. Your own limits on every number, a dry-run executor kit to wire up first, executor health, paper vs real fills, and the daily digest. What dexterm does, and what it never does. Experimental; not financial advice.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-changed-in-0-1-7.md

@@ -0,0 +1,26 @@
+---
+id: docs-live-trading-changed-in-0-1-7
+title: Live trading › Changed in 0.1.7
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: Changed in 0.1.7
+anchor: changed-in-0-1-7
+url: https://dexterm.xyz/docs/live-trading#changed-in-0-1-7
+tags:
+  - docs
+  - live-trading
+  - changed
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+Earlier 0.1.7 test builds had an experimental local live signer with a dedicated trading wallet, and a LIVE trade ticket signed in Phantom. Both were removed before release, because dexterm should not hold a key. Sending a strategy's trades to an executor of your choice automatically is real mode (https://dexterm.xyz/docs/real-mode), new in 0.2.0, still with no key in dexterm.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-real-mode-your-strategy-s-trades-to-your.md

@@ -0,0 +1,31 @@
+---
+id: docs-live-trading-real-mode-your-strategy-s-trades-to-your
+title: Live trading › Real mode: your strategy's trades to your executor (0.2.0, experimental)
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: Real mode: your strategy's trades to your executor (0.2.0, experimental)
+anchor: real-mode-your-strategy-s-trades-to-your-executor-0-2-0-experimental
+url: https://dexterm.xyz/docs/live-trading#real-mode-your-strategy-s-trades-to-your-executor-0-2-0-experimental
+tags:
+  - docs
+  - live-trading
+  - real
+  - mode
+  - strategy
+  - trades
+  - executor
+  - experimental
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+In real mode (https://dexterm.xyz/docs/real-mode) a strategy you armed on your own terminal sends every buy and sell it decides to your executor as a LIVE TRADE FIRE signal: a local webhook, a command, a stream file or MCP (a bot cannot read another bot's messages), with a copy in your Telegram chat. Your executor holds the wallet and acts on it; dexterm still holds no key and signs nothing. Hard caps, a kill switch (`dexterm autotrade signal kill`) and receipts of what your executor did are all on your machine. Experimental; not financial advice.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-stopping.md

@@ -0,0 +1,28 @@
+---
+id: docs-live-trading-stopping
+title: Live trading › Stopping
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: Stopping
+anchor: stopping
+url: https://dexterm.xyz/docs/live-trading#stopping
+tags:
+  - docs
+  - live-trading
+  - stopping
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+- `/kill` from your paired chat, `dexterm autotrade stop`, or Ctrl-C in the runner stops a paper run.
+- `dexterm wallet panic` engages the kill switch: every autotrade run and the paper agent desk halt, and nothing starts again until `dexterm wallet resume` (a keypress on a real terminal).
+- To stop live trades, use your trading bot's own controls. dexterm cannot stop them.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-the-short-version.md

@@ -0,0 +1,34 @@
+---
+id: docs-live-trading-the-short-version
+title: Live trading › The short version
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: The short version
+anchor: the-short-version
+url: https://dexterm.xyz/docs/live-trading#the-short-version
+tags:
+  - docs
+  - live-trading
+  - short
+  - version
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+> **0.2.0, experimental:** dexterm never holds a key and never signs. Live trades happen in the executor you choose (a Telegram trading bot behind your own relay, or any script): in real mode (https://dexterm.xyz/docs/real-mode) your strategy sends it a signal for each trade, and it acts by its own rules. Not financial advice.
+
+- **dexterm never holds a key and never signs a transaction.** It has no trading wallet, no signer and no place to keep a private key. It builds no transaction and sends none.
+- **Live trading happens in a Telegram trading bot of your choice.** That bot holds its own wallet and places the orders. You pick it, you fund it, and its rules and fees are its own.
+- **dexterm's part is the Telegram connector (https://dexterm.xyz/docs/telegram).** Through your own bot, dexterm sends alerts, signals and run control to your chat. You read them and act in the trading bot yourself.
+- **Everything else in dexterm is paper or read-only:** the screener, the analyst, MCP, paper trading (https://dexterm.xyz/docs/paper-trading) and autotrade (https://dexterm.xyz/docs/autotrade) on paper.
+
+> **Not financial advice.** Memecoins rug, pools drain and quotes move. Whatever you trade live, you trade in your trading bot, with money you are ready to lose.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-using-a-trading-bot-with-dexterm.md

@@ -0,0 +1,31 @@
+---
+id: docs-live-trading-using-a-trading-bot-with-dexterm
+title: Live trading › Using a trading bot with dexterm
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: Using a trading bot with dexterm
+anchor: using-a-trading-bot-with-dexterm
+url: https://dexterm.xyz/docs/live-trading#using-a-trading-bot-with-dexterm
+tags:
+  - docs
+  - live-trading
+  - using
+  - trading
+  - bot
+  - dexterm
+  - live
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+1. Pick a Telegram trading bot you trust, and read its own terms, fees and security advice. Fund its wallet with only what you are ready to lose.
+2. Set up dexterm's own bot for your chat: `dexterm telegram setup`, then `dexterm telegram pair`. See Telegram (https://dexterm.xyz/docs/telegram). This is a separate bot that only talks to you.
+3. Run a strategy on paper (`dexterm autotrade run <id> --paper`). Its alerts arrive in your chat.
+4. When you want to act on one, do it in your trading bot.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-what-dexterm-does-not-do.md

@@ -0,0 +1,30 @@
+---
+id: docs-live-trading-what-dexterm-does-not-do
+title: Live trading › What dexterm does not do
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: What dexterm does not do
+anchor: what-dexterm-does-not-do
+url: https://dexterm.xyz/docs/live-trading#what-dexterm-does-not-do
+tags:
+  - docs
+  - live-trading
+  - dexterm
+  - does
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+- It does not place an order in your trading bot for you. In real mode (https://dexterm.xyz/docs/real-mode) it sends your executor a signal; your executor places the order, by its own rules.
+- It does not hold, import, create, decrypt or ask for a private key or seed phrase. Anything that asks you for one is not dexterm.
+- It does not sign or send a transaction. `dexterm wallet link` only proves which wallet is yours with a signed **message** in Phantom; dexterm keeps the public key to show your address. It never asks Phantom to sign a transaction.
+- It does not know what your trading bot did. Positions, fills and P/L in dexterm are paper.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading-what-dexterm-does.md

@@ -0,0 +1,29 @@
+---
+id: docs-live-trading-what-dexterm-does
+title: Live trading › What dexterm does
+kind: docs
+page: live-trading
+page_title: Live trading
+heading: What dexterm does
+anchor: what-dexterm-does
+url: https://dexterm.xyz/docs/live-trading#what-dexterm-does
+tags:
+  - docs
+  - live-trading
+  - dexterm
+  - does
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+- **Finds and explains.** The screener, the token screen, the LARP check (https://dexterm.xyz/docs/larp) and the analyst (https://dexterm.xyz/docs/analyst) read public data. None of them can trade.
+- **Practises on paper.** The paper ticket, paper accounts (https://dexterm.xyz/docs/autotrade#paper-accounts) and paper autotrade runs (the yolo preset (https://dexterm.xyz/docs/yolo) included) fill on a simulated book on your machine.
+- **Tells you in Telegram.** With Telegram (https://dexterm.xyz/docs/telegram) set up and paired, a paper run sends candidates, entries, exits, halts and a daily summary to your chat, and takes `/status`, `/pause`, `/resume`, `/kill`, `/flatten` and `/use` from it.

package/dist/packages/mcp/assets/kb/docs/docs-live-trading.md

@@ -0,0 +1,23 @@
+---
+id: docs-live-trading
+title: Live trading
+kind: docs
+page: live-trading
+page_title: Live trading
+url: https://dexterm.xyz/docs/live-trading
+tags:
+  - docs
+  - live-trading
+  - live
+  - trading
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/live-trading.md
+date: 2026-10-16
+---
+
+dexterm never holds a key and never signs a transaction. Live trading happens in a Telegram trading bot of your choice; dexterm's part is the Telegram connector, which sends alerts, signals and run control to your chat. Not financial advice.

package/dist/packages/mcp/assets/kb/docs/docs-ollama-another-machine.md

@@ -0,0 +1,28 @@
+---
+id: docs-ollama-another-machine
+title: Use a local model with Ollama › Another machine
+kind: docs
+page: ollama
+page_title: Use a local model with Ollama
+heading: Another machine
+anchor: another-machine
+url: https://dexterm.xyz/docs/ollama#another-machine
+tags:
+  - docs
+  - ollama
+  - another
+  - machine
+  - use
+  - local
+  - model
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/ollama.md
+date: 2026-10-16
+---
+
+`dexterm ai host http://<machine>:11434` points dexterm at an Ollama on another computer you control. Prompts, screen context and tool results then travel over your network, and `dexterm ai status`, `dexterm doctor` and each chat answer say so. dexterm contacts no other host for the local engine. It never follows a redirect: if the host answers with one, dexterm sends nothing on, and `dexterm doctor` and the chat answer say the host redirected.

package/dist/packages/mcp/assets/kb/docs/docs-ollama-autotrade-on-a-local-model.md

@@ -0,0 +1,29 @@
+---
+id: docs-ollama-autotrade-on-a-local-model
+title: Use a local model with Ollama › Autotrade on a local model
+kind: docs
+page: ollama
+page_title: Use a local model with Ollama
+heading: Autotrade on a local model
+anchor: autotrade-on-a-local-model
+url: https://dexterm.xyz/docs/ollama#autotrade-on-a-local-model
+tags:
+  - docs
+  - ollama
+  - autotrade
+  - local
+  - model
+  - use
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/ollama.md
+date: 2026-10-16
+---
+
+`dexterm autotrade run <strategy> --paper --engine ollama` (or `dexterm ai engine ollama --surface autotrade`) runs each candidate's session on your local model. The session has no tools: the request to Ollama never carries any, so the model can only answer. Its reply is constrained to `{comment, decision}` and turned into the same `DECISION {…}` line a Claude session writes, so the same closed schema, clamp, caps and run file apply. A reply later than the strategy's decision window is no answer. `--model <name>` picks another local model for the run. The run file records `agent: ollama`, the model and $0.
+
+The runner needs the `paper` profile and refuses to start below it, with the command that raises it.

package/dist/packages/mcp/assets/kb/docs/docs-ollama-check-your-model-dexterm-ai-probe.md

@@ -0,0 +1,38 @@
+---
+id: docs-ollama-check-your-model-dexterm-ai-probe
+title: Use a local model with Ollama › Check your model: dexterm ai probe
+kind: docs
+page: ollama
+page_title: Use a local model with Ollama
+heading: Check your model: dexterm ai probe
+anchor: check-your-model-dexterm-ai-probe
+url: https://dexterm.xyz/docs/ollama#check-your-model-dexterm-ai-probe
+tags:
+  - docs
+  - ollama
+  - check
+  - model
+  - dexterm
+  - probe
+  - use
+  - local
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/ollama.md
+date: 2026-10-16
+---
+
+`dexterm ai probe` checks that Ollama answers, the model is pulled, it can call tools, and how much context it has. `dexterm ai probe --json` also asks it three short trading questions and checks it answers in the decision format the AUTOTRADE runner needs. It warns when the model is below the bar for your profile:
+
+| profile | tool calling | context | decision format |
+|---|---|---|---|
+| `observe` | optional | ≥ 4,096 | not needed |
+| `propose` | yes | ≥ 8,192 | not needed |
+| `paper` | yes | ≥ 8,192 | 2 of 3 |
+| `full` | yes | ≥ 16,384 | 3 of 3 |
+
+A decision a model cannot format is refused by the engine, which means fewer trades, never bigger ones.

package/dist/packages/mcp/assets/kb/docs/docs-ollama-how-we-checked.md

@@ -0,0 +1,27 @@
+---
+id: docs-ollama-how-we-checked
+title: Use a local model with Ollama › How we checked
+kind: docs
+page: ollama
+page_title: Use a local model with Ollama
+heading: How we checked
+anchor: how-we-checked
+url: https://dexterm.xyz/docs/ollama#how-we-checked
+tags:
+  - docs
+  - ollama
+  - checked
+  - use
+  - local
+  - model
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/ollama.md
+date: 2026-10-16
+---
+
+Offline tests drive a fake Ollama server through the real app paths and the real dexterm MCP server: tool round trips, the tool list each profile offers, refused calls that never run, the no-tools mode, structured verdicts, the typed `full` confirmation, and the doctor lines. The firewall test checks the local model receives exactly the text the Claude CLI receives. The caps test runs the same decisions through the Claude path's session interface and a local session over a recorded tape and gets identical clamps, refusals and fills. Answer quality and speed of local models against Claude have not been benchmarked.

package/dist/packages/mcp/assets/kb/docs/docs-ollama-models-without-tool-calling.md

@@ -0,0 +1,32 @@
+---
+id: docs-ollama-models-without-tool-calling
+title: Use a local model with Ollama › Models without tool calling
+kind: docs
+page: ollama
+page_title: Use a local model with Ollama
+heading: Models without tool calling
+anchor: models-without-tool-calling
+url: https://dexterm.xyz/docs/ollama#models-without-tool-calling
+tags:
+  - docs
+  - ollama
+  - models
+  - without
+  - tool
+  - calling
+  - use
+  - local
+  - model
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/ollama.md
+date: 2026-10-16
+---
+
+If the model cannot call tools, dexterm fetches the selected coin's dossier itself and the model answers from it, and the answer starts with `(… has no tool calling: answering from the dossier without tools)`. Structured verdicts carry a `no_tools_mode` flag. For tool use pull a tool-capable model (the table above).
+
+A local model that keeps asking for a tool it does not have is refused each time (the call never runs); after three refusals the turn stops and says so.

package/dist/packages/mcp/assets/kb/docs/docs-ollama-pick-the-engine-globally-or-per-surface.md

@@ -0,0 +1,43 @@
+---
+id: docs-ollama-pick-the-engine-globally-or-per-surface
+title: Use a local model with Ollama › Pick the engine, globally or per surface
+kind: docs
+page: ollama
+page_title: Use a local model with Ollama
+heading: Pick the engine, globally or per surface
+anchor: pick-the-engine-globally-or-per-surface
+url: https://dexterm.xyz/docs/ollama#pick-the-engine-globally-or-per-surface
+tags:
+  - docs
+  - ollama
+  - pick
+  - engine
+  - globally
+  - per
+  - surface
+  - use
+  - local
+  - model
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/ollama.md
+date: 2026-10-16
+---
+
+`dexterm ai engine <auto|claude|codex|ollama>` sets the engine for everything; add `--surface analyst|autotrade|agent` to set one surface only (for example the analyst on Claude and paper autotrade on the local model). `dexterm ai status` shows the engine for each surface, the local model, the profile and a quick probe; `dexterm ai status --parity` adds the full list of what runs where.
+
+For the analyst the order is: `--analyst-engine`, then `DEXTERM_ANALYST_ENGINE`, then `analyst.engine` in `config.json`, then `ai.json`, then `auto`. **`auto` is unchanged**: Claude Code when it is installed, else Codex, else the local model once you set one up (or Ollama is installed). With none of them, the analyst says how to set up an AI backend, and `dexterm doctor` lists all three ways.
+
+The settings live in `~/.dexterm/ai.json` (mode 0600). Only you write it, with `dexterm ai …` or by hand. No MCP tool, chat message, Telegram command or model output can change it.
+
+| setting | how |
+|---|---|
+| engine | `dexterm ai engine ollama` · `DEXTERM_AI_PROVIDER` · per surface `--surface S` |
+| model | `dexterm ai model <name>` · `DEXTERM_OLLAMA_MODEL` (when none is set dexterm picks the first suggested model you pulled) |
+| host | `dexterm ai host <url>` · `DEXTERM_OLLAMA_HOST` (default `http://127.0.0.1:11434`) |
+| context | `dexterm ai ctx <tokens>` |
+| profile | `dexterm ai restrictions observe|propose|paper` · `dexterm ai engine ollama --full` · `DEXTERM_AI_RESTRICTIONS` can only lower it |

package/dist/packages/mcp/assets/kb/docs/docs-ollama-restriction-profiles.md

@@ -0,0 +1,35 @@
+---
+id: docs-ollama-restriction-profiles
+title: Use a local model with Ollama › Restriction profiles
+kind: docs
+page: ollama
+page_title: Use a local model with Ollama
+heading: Restriction profiles
+anchor: restriction-profiles
+url: https://dexterm.xyz/docs/ollama#restriction-profiles
+tags:
+  - docs
+  - ollama
+  - restriction
+  - profiles
+  - use
+  - local
+  - model
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/ollama.md
+date: 2026-10-16
+---
+
+| profile | the local engine may |
+|---|---|
+| `observe` | analyse only: the read tools, no UI actions, no proposals, no orders |
+| `propose` | everything the analyst does on Claude: the read tools, the UI actions (open a coin, the screener, the watchlist, a feed, and open a PAPER ticket that you confirm), and strategy proposals you apply with a key. No orders. |
+| `paper` | `propose`, plus paper orders: the AUTOTRADE runner's paper sessions, agent paper trading (https://dexterm.xyz/docs/agents) inside a mandate you armed, starting or stopping one of your parallel strategies (https://dexterm.xyz/docs/autotrade#several-strategies-at-once), paper journal tags and backtest requests |
+| `full` | everything the Claude path may do, inside the same caps, mandate tiers and kill switch |
+
+**A new local setup starts at `propose`.** `paper` is one command: `dexterm ai restrictions paper`. **`full` needs a typed confirmation** on a real terminal: `dexterm ai engine ollama --full` explains the small-model risk and asks you to type `ENABLE FULL`. It is recorded for that one model: change the model and the engine runs at `paper` until you confirm again. Going back to a lower profile forgets the confirmation. It needs you at a real terminal: a pipe cannot confirm it.