Delegates coding tasks to local models with a safety layer that verifies patches through static analysis and real test runs.
Also known as pvnc228/local-coding-agent, local-coding-agent
- Stars
- 11
- Tools
- —
- Downloads, 30 days
- 616
- Latest version
- 1.2.0
- Last commit
- Nov 3, 2026
- License
- MIT
What is Local Coding Agent MCP?
Local Coding Agent delegates coding tasks to local models with a safety layer that verifies patches through static analysis and real test runs.
Summary generated from the project's README
About Local Coding Agent MCP server
Local Coding Agent provides a controlled execution environment for delegating coding tasks from cloud-based AI agents to models running on your own machine. It acts as a safety layer that prevents local models from having unrestricted shell or write access to your workspace. Instead, the system uses a controller to verify every proposed change through static analysis and real external test runners before any code is permanently applied.
Developers can integrate this server with existing tools like Claude Code, Cursor, Windsurf, or Cline using the Model Context Protocol. The setup requires Python 3.10 or newer and a local inference engine such as Ollama. Users can interact with the system via a Windows Desktop Harness for a visual interface or through a CLI for terminal-based workflows and CI integration. The software manages file scopes and can automatically roll back changes if post-apply checks fail, ensuring your repository remains stable.
What you can do with it
- 1Delegate focused coding tasksHand a specific coding goal to a local model while keeping the main cloud agent in control of the larger project.
- 2Verify code changes with testsEnsure that any code proposed by a local model passes your existing test suite before it is applied to your files.
- 3Automate safe code rollbacksAutomatically revert any code modifications that cause a failure in your configured post-apply checks.
- 4Integrate local models into IDEsConnect your local inference server to professional coding environments using MCP or Agent Skills.
Written from the project's README. Every use case is checked against a quote from it.
How to install Local Coding Agent MCP
Formats verified 10 Nov 2026Install Local Coding Agent MCP in Claude Code
$ claude mcp add local-coding-agent -- uvx local-coding-agentInstall Local Coding Agent MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"local-coding-agent": {
"command": "uvx",
"args": [
"local-coding-agent"
]
}
}
}Install Local Coding Agent MCP in VS Code
.vscode/mcp.json
{
"servers": {
"local-coding-agent": {
"type": "stdio",
"command": "uvx",
"args": [
"local-coding-agent"
]
}
}
}Install Local Coding Agent MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"local-coding-agent": {
"command": "uvx",
"args": [
"local-coding-agent"
]
}
}
}Install Local Coding Agent MCP in Codex
~/.codex/config.toml
[mcp_servers.local-coding-agent] command = "uvx" args = ["local-coding-agent"]
Install Local Coding Agent MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"local-coding-agent": {
"command": "uvx",
"args": [
"local-coding-agent"
]
}
}
}Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablepvnc228/local-coding-agent is public and reachablegithub.com/pvnc228/local-coding-agent ↗Pass
- Package names this repository as its sourcelocal-coding-agent names pvnc228/local-coding-agent as sourcepypi.org/project/local-coding-agent/ ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for local-coding-agentpypi.org/project/local-coding-agent/ ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-03github.com/pvnc228/local-coding-agent ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from local-coding-agentPass
- No critical advisory in the package or its dependencies29 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubLocal Coding Agent
Local execution and safety layer for delegating coding tasks from cloud agents to models on your own machine.
What is Local Coding Agent?
Local Coding Agent lets a cloud coding agent delegate a narrow task to a local model without giving that model unrestricted access to your repository. Connect Codex, Claude Code, Cursor, Windsurf, Cline, OpenCode, Antigravity, or another compatible harness through MCP, the reusable Agent Skill, or the local-agent CLI. The cloud agent stays in charge of the larger task; Local Coding Agent supplies the controlled local execution path.
The calling agent sends a focused goal, a workspace, an allowlist of files, and checks. Your local model returns a proposal for review. The local model proposes; the controller verifies. A change is only reported as applied after the declared file scope held, the patch passed static analysis, and a real external test runner confirmed the configured checks. If a post-apply check fails, the change is rolled back and the rollback is itself verified against recorded file digests. The local model does not receive unrestricted shell or write access to your workspace.
Use the Desktop Harness when you want a Windows interface for local chat, model selection, sessions, task status, and change review. Use the CLI for terminals, scripts, CI, or direct integration with a coding harness. Both use the same controller and safety rules.
You keep control of Git and delivery. Local Coding Agent does not create commits, push branches, publish releases, or download a model on its own.
What the gate refuses
The same gate backs apply_proposal, local-agent apply, and the desktop apply action:
- A patch that touches a file outside the declared scope is rejected before the workspace is touched (
error.kind: patch_outside_scope). - An apply with no targeted check is refused — no external evidence, no apply (
error.kind: apply_requires_checks). - A patch that fails the post-apply checks is rolled back; the result is
"rejected"witherror.kind: post_apply_check_failed. - A rollback that cannot be confirmed against the recorded baseline is reported as
workspace_modified: truewithworkspace_state: "unknown"and risk kindrollback_failed— never as a clean restore.
Choose your download
Current public release: v1.2.0
Choose the CLI release for terminal workflows, scripts, CI, or integration with another AI coding environment. It provides the local-agent command, MCP server, Agent Skill, diagnostics, sessions, model tools, and task delegation.
Download the CLI wheel or CLI source archive. Windows users can download the Desktop Harness installer and verify the published files with SHA256SUMS.txt.
The v1.2.0 release contains the CLI archives and the Windows Desktop Harness installer. Local inference remains local; install Ollama or run a compatible local model server before requesting live model responses.
Desktop Harness
Open the Harness, choose a workspace, select a local model, and start working. The desktop application brings the complete local coding workflow into one focused interface:
- Interactive Chat for questions, explanations, and everyday coding work.
- Chat, Build, Plan, and Auto modes for different kinds of requests.
- Delegated Tasks for handing a focused coding change to a local model.
- Workspace sessions so you can return to previous conversations and tasks.
- Model discovery, model profiles, context settings, hardware telemetry, and diagnostics.
- Clear status messages when the local backend is ready, unavailable, or needs attention.
- Reviewable code changes and checks before changes are applied.
The 30-second tour below follows one delegated change: the local model proposes, the controller checks scope, a real test runner decides, and a failed check rolls the change back. Click it for the video with sound.
CLI installation
Requirements:
- Python 3.10 or newer.
- Git on
PATHfor workspace operations. - Ollama or an OpenAI-compatible local model server for live inference.
Install the CLI package:
pipx install local-coding-agent
Or install from a checkout:
git clone https://github.com/pvnc228/local-coding-agent.git
cd local-coding-agent
python -m pip install -e .
Check the installation:
local-agent doctor
local-agent test-run --mock
Add --json where supported when the output will be consumed by another tool.
Connect another AI coding agent
Local Coding Agent can provide its capabilities to other AI coding environments through MCP or an Agent Skill:
local-agent init-mcp --auto --write
local-agent init-skill --write
Start the MCP server manually when a client needs an explicit command:
local-agent serve-mcp --workspace . --enable-tasks
See local_coding_agent/docs/MCP_INTEGRATION.md for client configuration examples and skills/local-coding-agent/SKILL.md for the reusable Agent Skill.
A typical coding request
- Choose a workspace and a local model.
- Ask a question or describe the change you want.
- Inspect the suggested code change in the application.
- Run the relevant checks and apply the change when it looks right.
The application keeps the workflow understandable: you can see what is being changed, which checks are being run, and whether the local backend is available. Commits, tags, pushes, and publishing remain under your control.
CLI commands
| Command | Purpose |
|---|---|
local-agent delegate |
Give a focused coding task to a local model. |
local-agent decompose |
Break a larger request into smaller coding tasks. |
local-agent apply |
Apply a reviewed change and run its checks. |
local-agent chat |
Run a prompt or a persistent chat session. |
local-agent sessions |
List or inspect saved sessions. |
local-agent profiles |
Inspect configured model profiles. |
local-agent memory |
Inspect model memory and VRAM settings. |
local-agent calibrate |
Calculate safe worker bounds for a VRAM budget. |
local-agent benchmark |
Run the local coding benchmark. |
local-agent doctor |
Diagnose Python, Git, Ollama, RAM, VRAM, and models. |
local-agent monitor |
Serve the local metrics dashboard. |
local-agent test-run --mock |
Run deterministic local workflow checks. |
Examples:
local-agent chat "Explain what context_manager.py does"
local-agent chat --repl --session-id refactor-session
local-agent delegate --task task.json --model qwen2.5-coder:7b --json
local-agent apply --patch-file patch.diff --workspace . --file src/foo.py --check "pytest tests/"
local-agent monitor --port 8765
Open http://127.0.0.1:8765/dashboard to view queue load, latency, tokens per second, and change records.
The CLI also exposes preview surfaces that are not part of the stable contract and may change without notice: ui/app, lsp, serve-acp, skeletonize, lint-patch, scan-models, spill-read, and grep. The stable, tested set is the table above plus desktop, chat, serve-mcp, init-mcp, and init-skill.
Field results & limitations
The published numbers come from a 20-task suite, so treat them as directional rather than settled:
- On that suite,
qwen3.8-27b-q4scored 100.0% correctness with a 95% Wilson interval of [83.9%, 100.0%], andqwen3-8b-q6kscored 90.0% [69.9%, 97.2%]. The wide intervals are the small sample size, not a rounding artifact. - Small models handle single-file work in this harness; cross-file coordination (Tier 3 in the capability ladder) needs the host agent to decompose the task into atomic envelopes first.
- Results are model and hardware specific. Reproduce them with
local-agent benchmarkbefore relying on any figure.
See local_coding_agent/docs/BENCHMARK.md for the methodology and the full table.
Local models
Model profiles describe the provider, model, context window, generation limits, and keep-alive behavior. The Harness can discover installed Ollama models and local GGUF files, while the CLI exposes the same information for scripts and integrations.
local-agent profiles list --json
local-agent memory status --json
Documentation
- Quickstart
- FAQ
- MCP integration
- Security policy
- Changelog
- Architecture reference
- Protocol reference
- Benchmark methodology
- Roadmap
- Runtime setup tips: context, KV cache, thinking and CPU limits
The same pages open inside the Desktop Harness under Help, and local-agent help-docs prints them in a terminal.
License
Local Coding Agent is distributed under the MIT License.
Local Coding Agent MCP questions
How do I add Local Coding Agent MCP to Claude Code?
Run claude mcp add local-coding-agent -- uvx local-coding-agent in your terminal. Add --scope user to make it available in every project.
How do I add Local Coding Agent MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does the local model have unrestricted access to my repository?
No, the local model does not receive unrestricted shell or write access to your workspace; it provides proposals that are verified by a controller.
What happens if a code patch fails the post-apply checks?
If a post-apply check fails, the change is automatically rolled back and the rollback is verified against recorded file digests.
Can I use this with existing AI coding tools like Cursor or Claude Code?
Yes, you can connect compatible harnesses like Codex, Claude Code, Cursor, Windsurf, Cline, and others through MCP or the Agent Skill.
Does the agent handle Git operations like committing or pushing?
No, the agent does not create commits, push branches, or publish releases; you maintain full control over Git and delivery.