LLMatic Agent RuntimeLLMatic brings a deterministic local software-engineering workflow to VS Code and AI coding agents. It keeps runtime state outside your repository, integrates with Kilo Code through MCP, and helps you move from project discovery to an approved engineering plan, implementation, validation, review, and task progression. InstallFrom VS Code Marketplace
CLI:
From a VSIXDownload the matching VSIX from the GitHub Release and use:
or:
First runOpen the Command Palette with
Get Ready attaches the workspace externally, verifies the bundled runtime, inspects required project tools, connects Kilo Code when enabled, and validates the global LLMatic MCP registration. The LLMatic Activity Bar view shows one canonical state:
New project workflowOpen an empty folder and run:
LLMatic asks what you want to build and guides the major engineering decisions. Discovery is saved outside the repository. When discovery is complete:
The private plan can include:
You can review artifacts, edit decisions, request changes, and regenerate the plan. Requested changes are applied to the next draft. Repository files remain untouched until you explicitly choose Approve & Initialize. Existing repository workflowFor an existing codebase:
Then use LLMatic's agent, review, and task workflows as needed. Task sources are detected in this order:
Kilo CodeKilo Code is the default coding-agent integration. LLMatic registers its verified MCP runtime in Kilo Code's global MCP configuration. If Kilo Code is installed while onboarding is in progress, LLMatic resumes Get Ready automatically. The default direct-agent model is:
Configure another model with:
LLMatic shows a data-handling warning before first use of Auto Free. Use an appropriate model/provider for confidential repositories. Gateway API keyKilo Code MCP connectivity works without a Gateway API key. The key is needed only for LLMatic's direct Gateway Agent and automated review/fix orchestration. Use Set Kilo Gateway API Key in the LLMatic Activity Bar or run:
LLMatic opens a password input and stores the value only in VS Code SecretStorage. Starting a direct agent or review without a key also offers this setup automatically. Core commands
SafetyLLMatic runtime state is stored in VS Code global storage rather than in the opened repository. The built-in fix agent does not receive unrestricted shell, package-install, Git push, PR merge, deployment, or remote-database mutation capabilities. Human approval is required before a greenfield private plan becomes repository state. Gateway credentials are stored in VS Code SecretStorage. TroubleshootingStart with:
For runtime integrity problems:
For Kilo MCP problems:
For setup state:
When reporting a bug, include your VS Code version, LLMatic version, operating system, relevant LLMatic output-channel diagnostics, and reproducible steps. Support and sourceSource code, issue tracking, release artifacts, and engineering documentation: https://github.com/pikkst/llmatic-agent-runtime LicenseMIT. |