Skip to main content

Iterative Generation

The Svantic terminal can orchestrate multi-step Forge workflows conversationally. Instead of running individual CLI commands, you describe what you want and the terminal reads your files, proposes tools, lets you refine, scans additional sources, and composes the final agent — all in one session. This page walks through a typical iterative session.

The Workflow

Step 1: Propose Tools from Source Code

Start by telling the terminal what you have:
The terminal reads every file in src/monitoring/, analyzes the exports and JSDoc comments, then calls forge_propose_tools internally. You see a response like:

Step 2: Refine the Proposal

Tell the terminal what to change:
The terminal updates its internal proposal. No code is generated yet.

Step 3: Generate the Tools

The terminal calls forge_generate_tools with the finalized proposal. It produces:
  • monitoring.tool-spec.yaml
  • monitoring.capabilities.ts
The terminal confirms:

Step 4: Compose Everything

The terminal calls compose with both tool specs:

Step 5: Make Adjustments

You can keep iterating:
The terminal updates the tool spec and regenerates:

Terminal Functions Reference

These are the Forge functions the terminal calls behind the scenes:

When to Use Iterative vs CLI

Tips

  • The terminal remembers context within a session. You can refer to “the monitoring tools” or “that Slack file” without repeating paths.
  • Ask the terminal to explain a generated tool spec before generating code: “Show me what the tool spec looks like for list_active_alerts.”
  • If you are unsure what functions a file exports, ask: “What functions are in src/monitoring/alerts.ts?”
  • You can mix generation paths in one session: scan some files, generate from a prompt, pull from an OpenAPI spec, then compose everything together.