7.4 KiB
jcode
A minimal, single-file coding agent (< 1000 lines of Python) for local LLMs — with optional cloud fallback.
jcode connects to a local LM Studio or Ollama server (or, via settings.json, to OpenAI, Anthropic, or Gemini), takes a task in plain language, and works autonomously inside a sandboxed ./code directory: it reads, writes, and edits files, runs commands, writes its own smoke tests, and keeps fixing the code until the tests pass.
_ _
(_) ___ ___ __| | ___
| |/ __/ _ \ / _ | / _ \
| | (_| (_) | (_| || __/
_/ |\___\___/ \____| \___|
|__/
Features
- Autonomous test-fix loop — the agent writes a test for every change, runs it, analyzes failures, fixes the code, and repeats until green (up to
MAX_STEPS, default 40). - Sandboxed — all file operations are confined to
./code; path-escape attempts (../, absolute paths) are blocked. Destructive shell commands (rm -rf /,sudo,dd,mkfs, shutdown, fork bombs,curl | sh, …) are refused. - Zero-config local backends — auto-detects LM Studio (port 1234) first, then Ollama (port 11434).
- Cloud providers via
settings.json— switch to OpenAI, Anthropic, or Gemini at runtime with/backend <name>; all are used through their OpenAI-compatible endpoints, so the singleopenaiclient dependency covers everything. - Project guidelines via
AGENTS.md— project-specific rules (coding style, per-language test conventions) are loaded fromcode/AGENTS.mdand injected as binding instructions. - Session-wide context management — token usage is tracked (server-reported or estimated); when the context nears its limit, older history is compacted into an LLM-written summary so long sessions keep working.
- Robust against flaky servers — visible retries with backoff; if the backend goes down, the session is preserved and the task can simply be resubmitted.
- Transparent — every request, tool call, and result is logged to
logFile.md; file changes are shown as colored unified diffs in the terminal. - Tools available to the model —
list_files,read_file(optionally with line numbers),search_files(regex grep over the sandbox, hits asfile:line: content),write_file,edit_file(search/replace),insert_lines,delete_lines,run_command,web_search(DuckDuckGo),fetch_url.
Requirements
- Python 3.10+
pip install openai prompt_toolkit ddgs- One of:
Usage
# One-shot task
python jcode.py "Write fib.py with fib(n) and a smoke test that checks fib(10)==55."
# Interactive mode (multiline input; history is kept across tasks)
python jcode.py
All generated files land in ./code, which is created automatically.
Interactive commands
| Command | Effect |
|---|---|
/status |
Show context usage, message counts, model, sandbox |
/new, /neu, /reset |
Clear the session history |
/models |
List models available on the current backend |
/model <name> |
Switch model |
/backend <name> |
Switch to lm-studio, ollama, or a provider from settings.json (e.g. openai, anthropic, gemini) |
/max-turns N |
Set the step limit per task |
Ctrl+C |
Quit |
Configuration
settings.json (optional)
Placed next to jcode.py. Defines cloud providers and, optionally, the backend to start on. API keys are read from environment variables — don't put literal keys in the file.
{
"default_provider": "",
"providers": {
"openai": {
"base_url": "https://api.openai.com/v1",
"api_key_env": "OPENAI_API_KEY",
"model": "gpt-4.1"
},
"anthropic": {
"base_url": "https://api.anthropic.com/v1/",
"api_key_env": "ANTHROPIC_API_KEY",
"model": "claude-sonnet-4-5"
},
"gemini": {
"base_url": "https://generativelanguage.googleapis.com/v1beta/openai/",
"api_key_env": "GEMINI_API_KEY",
"model": "gemini-2.5-pro"
}
}
}
default_provider: name of a provider to activate at startup; leave""to use the auto-detected local backend.- Each provider needs
base_url(an OpenAI-compatible endpoint),api_key_env(environment variable holding the key), and optionallymodel. - If the file is missing or malformed, jcode prints a warning and runs purely locally.
export ANTHROPIC_API_KEY=sk-ant-...
python jcode.py
Task> /backend anthropic
AGENTS.md (optional)
If code/AGENTS.md exists, it is loaded at session start and treated as binding project guidelines — e.g. "simplicity first", surgical changes only, and the per-language verification conventions (how to compile/test C, C++, Java, PHP, Python, HTML, CSS). Keeping language-specific rules here rather than in the system prompt keeps every request lean and lets you adapt conventions per project without touching code.
Constants in jcode.py
| Constant | Default | Meaning |
|---|---|---|
MODEL |
(auto) | Model name; auto-corrected to the first available model |
MAX_STEPS |
40 | Tool-use steps per task |
CMD_TIMEOUT |
60 s | Timeout per shell command |
CONTEXT_LIMIT |
256 000 | Model context window (tokens) |
COMPACT_THRESHOLD |
250 000 | History compaction kicks in above this |
REQUEST_TIMEOUT |
600 s | Timeout per LLM request (local models are slow) |
How it works
- The task is appended to the session history and sent to the model together with the tool schemas (derived automatically from the Python type annotations — no schema drift).
- The model plans, calls tools (read → edit → run test), and gets each result back.
- Failing tests loop back into analysis and fixes; only when the tests are green does the model answer with a summary and the turn ends.
- Near the context limit, the older history is summarized by the model itself and replaced, so the session can continue indefinitely.
Safety notes
jcode blocks known-destructive command patterns and confines file access to the sandbox, but run_command still executes shell commands on your machine with your user's permissions. Review logFile.md when in doubt, and treat web content fetched by the agent as untrusted data.
License
MIT License — Copyright (c) 2026 Prof. Dr. Joern Fischer
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.