Run repeatable commands
Use a consistent command pattern for market review, setup evaluation, paper entry notes, and post-trade review. Repeatability makes it easier to compare one simulated decision with the next.
Use case
Crypto trading CLI for paper trading
Use Trading Boy as a command-line workspace for crypto paper trading: define simulated entries, run repeatable review commands, capture alerts, and keep a journal trail that makes every rule change easier to inspect.
Why use a CLI for simulated crypto trading?
A crypto trading CLI helps turn a messy idea into a repeatable paper-trading process. Instead of manually copying setup notes, market context, risk limits, and post-trade reflections into disconnected tools, a command-line workflow can keep the same inputs visible every time. That matters when you are testing a process, because the goal is not to guess the next move. The goal is to learn whether your rules are clear enough to follow, whether the simulated decisions are reviewable, and whether the journal contains evidence that supports the next adjustment.
Trading Boy is intentionally paper-first. Trading Boy does not execute live trades, hold funds, or provide financial advice. The CLI workflow is built for simulated decisions, review prompts, risk checks, and learning loops. It is a way to practice structure before capital is involved, not a shortcut around research, risk management, or personal responsibility.
Keep paper risk visible
Attach paper size, invalidation, drawdown limits, and exposure notes to the workflow before a simulated entry is recorded. The CLI should show the risk rule, not hide it in a later spreadsheet.
Review before changing prompts
When paper results disappoint, inspect the command inputs, agent rationale, and journal tags before editing the workflow. Change one thing at a time so the next sample is meaningful.
CLI workflow layers
| Layer | What the CLI captures | Why it matters |
|---|---|---|
| Market frame | Token universe, time horizon, liquidity filters, trend context, and allowed setup types. | Prevents the paper agent from drifting into unrelated trades that cannot be compared. |
| Paper decision | Simulated entry, invalidation, target logic, paper size, and rationale. | Keeps the trade idea inspectable without implying a buy or sell recommendation. |
| Risk review | Maximum paper drawdown, correlated exposure, daily frequency, and stop conditions. | Shows whether the process respects boundaries even when no live funds are involved. |
| Alerts and journal | Telegram review prompts, exit notes, behavior tags, screenshots, and rule-fit outcomes. | Turns each simulated trade into evidence for the next paper workflow decision. |
Example command flow
1. Frame the session: Start with a paper-only command that names BTC, ETH, and SOL, uses a 4-hour review horizon, and requires the market to be above a defined trend filter.
2. Request a simulated decision: Ask the agent to mark a paper entry only if the setup, invalidation, paper size, and exposure notes are complete. If the setup is incomplete, the command should return "skip" with the missing rule.
3. Send review prompts: Route Telegram alerts to review channels as context. Alerts should explain what changed, what rule was tested, and what needs inspection; they should not be treated as live trade instructions.
4. Close the loop: After exit or expiry, record rule fit, paper result, behavior tag, and one next action: keep collecting samples, tighten the entry rule, reduce paper size, or pause the workflow.
Where the CLI fits
A command-line interface is useful when you want speed and auditability. Builders can keep workflows in version control, traders can rerun the same review prompts, and teams can compare paper runs without relying on memory. The best CLI flow is not the one with the most commands. It is the one where every command creates a clear record that can be checked later.
For background concepts, pair this page with the paper-trading guide, the backtesting versus paper trading explainer, and the forward testing guide.
Internal controls for CLI paper trading
- Require every simulated entry to include an invalidation rule.
- Block new paper entries when maximum paper drawdown is reached.
- Keep Telegram alerts labeled as review prompts, not trade signals.
- Tag each result by setup type, rule fit, and behavior pattern.
- Write down why a command, prompt, or risk rule changed.
Related pages
What a good paper CLI run produces
A useful crypto paper-trading CLI run produces more than a simulated profit or loss number. It produces a record of why a setup was eligible, what the agent believed it was testing, how much paper risk was assigned, what would invalidate the idea, and what review evidence should be checked afterward. If a paper result cannot be explained, it is hard to improve. If a paper result is documented in a consistent format, it can become part of a larger learning loop.
The same discipline applies to skipped trades. A skip can be valuable when the command names the reason: trend filter failed, liquidity was too thin, correlated exposure was already high, or the setup did not match the playbook. Over time, skipped setups can reveal whether the rules are too loose, too strict, or poorly described. A CLI makes those skips easy to store and compare because the command output has a consistent shape.
Paper-first safety checks
Use the CLI to slow down the workflow before it becomes emotional. Require a pre-trade note, a risk check, and a review tag before any simulated entry is accepted. If a command cannot explain the setup in plain language, the paper entry should be skipped or sent back for more context.
This boundary is especially important in crypto markets, where volatility can make a paper process look better or worse than it really is. Simulated outcomes do not prove that a live strategy will work, and a command-line workflow should never be used as a substitute for independent judgment.
Metrics worth tracking
- Completed paper runs by setup type.
- Rule-compliant entries versus command overrides.
- Paper drawdown by token group and market regime.
- Telegram alerts that led to useful review notes.
- Prompt changes made with evidence instead of frustration.
- Skipped setups with clear reasons.
When to keep collecting samples
Many CLI workflows fail because the rules change too quickly. One bad simulated trade may reveal a real issue, but it may also be noise. Before editing the command or prompt, check whether the paper sample is comparable to earlier runs. If the token, regime, holding period, or risk rule changed, the result may not belong in the same group.
Keep collecting samples when the journal is thin, the market frame changed, or the review question is still unclear. Adjust only after the same issue appears across enough comparable paper examples to make the change defensible.
When to pause the workflow
Pause the paper CLI workflow when commands produce unclear rationale, repeated rule violations, missing risk fields, or alerts that encourage action without review context. Pausing is not failure. It protects the quality of the dataset and prevents a weak process from generating more noise.
Use the pause to rewrite the market frame, reduce the token universe, simplify the setup, or add a stronger pre-trade review. Then resume with a narrower paper test.
FAQ
What is a crypto trading CLI for paper trading?
It is a command-line workflow for defining simulated crypto trades, reviewing rule fit, capturing paper results, and improving the process before live capital is considered.
Can Trading Boy place trades from the CLI?
No. Trading Boy does not execute live trades, hold funds, or provide financial advice. The CLI workflow is designed for paper trading, review, and evidence capture.
Who should use a crypto paper-trading CLI?
A CLI works well for traders, builders, and researchers who want repeatable simulated workflows, versioned prompts, auditable logs, and less manual copying between tools.
What should I review after a paper CLI run?
Review whether the command used the right market frame, followed the risk rule, produced useful Telegram alerts, and created journal notes that explain the next decision.
Paper trading boundary
Use Trading Boy to practice process quality, not to outsource trading decisions. Crypto paper trading is simulated, and the CLI should help you document assumptions, risk controls, review notes, and limits before any live-capital decision is considered.