Illumitech Forge CLI 1.4.0
Evidence-backed release execution, local web workbench and native interactive terminal.
After this candidate is published:
forge opens the terminal conversation in your Git project; outside a project it offers an
explicit project picker. forge --root PATH selects another project. State defaults to an
external per-project directory. illumitech-forge remains available for existing scripts.
The terminal includes an ASCII identity, Markdown, / command menu, F1 help, /status,
Ctrl+R session history, readline editing and native permission decisions. F2 or
/activities opens per-call and per-file details; arrows select, Enter/Space toggle
and Esc returns to the preserved draft. MCP failure indicators and file identities
survive bounded output truncation. Managed native
Codex authentication is preserved; Forge does not silently switch accounts, models or APIs.
ai-memory is optional. Chat text is not gate evidence, and publication is always explicit.
See the repository README for manifests, workbench, installation, support limits and credits. Windows and Claude remain experimental; this release's binary package targets macOS ARM64. Code is MIT; third-party notices and dependency inventory accompany the packages.
First execution without an agent
Creation prepares an example, without running it. The response includes inspect, dry-run, run and report commands using the same external state directory. Only Git is needed; the native evaluator is pinned by SHA-256 and verifies an artifact and preserved file.
init creates no memory routing by default. Explicit init --memory-workspace ID is opt-in
and preserves existing configuration. installation doctor inspects both executable names
without running unknown candidates. Status/report return 2 for stale evidence even if the
historical run snapshot remains passed. See the release verification for support limits.
Integrated workflows in 1.2.0
/plan REQUEST prepares structured work through the native client. Review the scope digest
and use /run DIGEST to authorize that scope. /tasks and /report ID expose state and evidence.
The Workbench offers the same workflow. Native permissions and declared final human gates
remain separate; scope consent never approves completion.
CLI automation includes workflow prepare|start|status|diagnose|resume|list|recipes|findings
and read-only eval compare. Bug regressions are frozen outside the project; dependency
remediation requires SARIF rescan plus project checks. Unknown usage stays unknown; the small
native pilot did not demonstrate token savings. Public GitHub uses MIT. The PT/EN website
remains a local preview, with no deployment, telemetry or native bridge.