CLI Workflow
March is designed to be used from the repository you are already working in.
You → march in the project directory
→ March reads current project facts
→ March edits or runs commands through explicit tools
→ March reports the resultStart a session
cd path/to/project
marchYou can also send one prompt directly:
march "explain how this package starts"Use --provider or --model when you want to override the configured default for the first model selection:
march --provider openai --model gpt-5.1What March sees
March does not assume the whole repository is already in the prompt. It starts with stable context, then reads files and command output when the task needs them.
That means a good request can be direct:
Find where provider configuration is loaded and explain the flow.March will locate the relevant files, open the parts it needs, and only then answer or edit.
Common loop
- Ask March to inspect or change something.
- Let it read the relevant files.
- Review the proposed or completed changes.
- Let it run a focused check, usually the fast test script for day-to-day work.
For project-specific rules, keep an AGENTS.md file in the repository. March loads it as part of project context so repeated instructions do not have to be pasted into every prompt.
Copy code from the TUI
Assistant answers may render fenced code blocks with borders and wrapping for readability. When you select text inside a code block, March copies the underlying source range instead of the decorated terminal cells:
- borders, padding, and ANSI styling are not copied;
- wrapped visual lines are merged back into the original source line;
- partial line selections preserve the selected source columns.
This keeps small snippets usable when you copy only part of a generated command, function, or config block.
Resume or inspect sessions
Use --resume <id> when you want to start from a previous pi session id:
march --resume <id>For debugging prompt assembly, --dump-context writes prompts under .march/context-dumps/:
march --dump-context