Reference and troubleshooting
CLI
Use the command line for validation, inspection, summaries, packaging, exports, and local agent installs.
Who this is for
Developers and power users who want repeatable automation using the same core as the app.
Before you start
- Install the CLI if distributed with your build.
- Have a kit folder available.
- Know the output path you want to write to.
Step-by-step guide
- 1
Run validate before sharing or installing a kit.
- 2
Use inspect or summarize to review a folder or repo.
- 3
Package with package for .agentkit.zip.
- 4
Export with export-onefile for .onefile.md.
- 5
List or render prepared prompts.
- 6
Use export-codex or export-claude-code for local agent targets.
- 7
See the CLI overview page for examples.
CLI
Forge Current step Inputs Output
1
2
Command preview Use the command line for validation, inspection, summaries, packaging, exports, and local agent installs.
3
Tips
- Use the CLI in scripts and checks.
- Keep generated outputs in a dist folder.
- The app and CLI share the same core concepts.
Common mistakes / troubleshooting
- Running commands from the wrong folder.
- Skipping validation before export.
- Confusing CLI exports with AI provider setup.