Expand description
The Balise CLI of one version, run through the balise launcher.
Each command is declared once in COMMANDS: its options, and a function that returns
data without printing anything. The terminal shows the data as compact text, --json as
JSON; the MCP server will serve the same commands as tools.
Modules§
- args
- Reading a command’s arguments from what its declaration allows.
- dev
- The dev supervisor, the same on the machine (
--native) and in the container (--inside): it watches the files, rebuilds, restarts the app, and writes one stream of logs. While a build runs, or fails, the last version that built keeps answering. - style
- Colors for a person at a terminal, with the conventions of Balise’s logs: codes in bold,
fix:in green,codein cyan, what is secondary dimmed. Agents,--jsonandNO_COLORget the plain text: colors would only cost them tokens.
Structs§
- Command
- One command of the CLI.
- Context
- What a command works with: where it runs, whether it may ask questions, and the machine.
- Failure
- Why a command failed, with its code and the exit code:
2for a wrong usage,1otherwise. - Report
- What a command returns: the text a person or an agent reads, and the same as data.
- System
- The real machine.
Constants§
- COMMANDS
- Every command, in the order help lists them.
Traits§
- Machine
- What the CLI needs to know about, or do on, the machine.
Functions§
- person_
at_ terminal - Whether a person is at the keyboard: standard input and output are a terminal, and the environment shows neither an agent nor CI.
- run
- Runs the command
argsnames. Returns what to print on standard output and the exit code.