You set how much it may do
Safe asks before every write and command. Balanced lets edits through and asks for commands. Full access never asks, yet still blocks destructive commands and writes outside the project.
JenderalCode reads, edits, runs tests and fixes, with whichever model you choose, while every write, command and push goes through a permission engine you control. Every change is checkpointed, so a bad idea is one click from undone.
Free and open source. Bring your own API key, or run local models with Ollama or LM Studio.
@@ -18,6 +18,9 @@ - router.post("/login", login); + const limit = rateLimit({ window: "1m", max: 5 }); + router.post("/login", limit, login);
A real workspace around the model: files, git, terminal, language servers and your own tools, wired through one permission engine and one undo button.
Safe asks before every write and command. Balanced lets edits through and asks for commands. Full access never asks, yet still blocks destructive commands and writes outside the project.
Files are snapshotted before the agent writes or deletes them. Restore a session's edits in one click, git or no git.
OpenAI, Anthropic, Google, DeepSeek, Mistral, xAI, Groq, Ollama and LM Studio. Switch per conversation, with live context and cost meters.
Plug in Playwright, Laravel Boost or any MCP server over stdio or HTTP. A project's .mcp.json runs only after you trust that exact file.
Claude Code, Codex, OpenCode and Antigravity in tabs next to the chat, kept running per project and resumed after a restart, with their subscription limits a click away.
After each edit, language servers (TypeScript, PHP, Python, Rust, Go) report errors straight back to the agent, so broken code gets fixed in the same turn.
Queue the next request or steer the running turn. Mention files with @, paste screenshots for vision models, and keep the agent's todo list in view.
Reuse SKILL.md playbooks from your projects and ~/.claude, run them as /commands, and hand research to read-only sub-agents with their own context.
The app checks for a new release when it starts and installs it with one click. Every update is signed and verified before it touches your machine.
The call becomes a concrete action: read, write, delete, run, fetch.
Paths are canonicalized; anything escaping the project, even via symlink, is caught.
The policy engine allows, denies, or asks you, with the diff or command in front of you.
Before a write or delete, the file is checkpointed so it can be restored.
With timeouts, output caps and process-group kill. Results go back to the model.
Repositories contain instructions, configs and scripts written by strangers. JenderalCode treats them that way.
API keys stay in your OS keychain or a 0600 file, never in the database, and are stripped from the environment of commands the agent runs.
Shell commands are parsed, not pattern-matched: pipes, subshells and bash -c are followed. Catastrophic commands are refused in every mode; git push asks unless you chose Full access.
Reading .env, private keys or credentials asks first (outside Full access). Edits are refused on files the agent hasn't read, or that changed since.
Project instructions are marked untrusted in the prompt. A repository's MCP servers never start until you trust that exact config.
A strict content policy: model output can't load remote resources, run scripts or navigate the app away.
Latest release: v0.1 · all releases
Drag the app to Applications, then run this once in Terminal (the app isn't notarized by Apple yet):
$ xattr -cr /Applications/JenderalCode.app
No Terminal? Open the app once, then System Settings → Privacy & Security → Open Anyway.
Run the installer. SmartScreen may warn because the installer isn't code-signed yet: choose More info → Run anyway.
The AppImage updates itself; make it executable with chmod +x. The .deb and .rpm packages are updated by reinstalling.
Yes. The app is MIT-licensed. You pay your model provider directly with your own API key, or nothing at all with local models.
Only what the agent sends to the model provider you pick, as context for its work. With Ollama or LM Studio, nothing leaves your machine. There is no JenderalCode server.
Yes. Open them in tabs next to the built-in agent. They run in your login shell with their own accounts, and JenderalCode shows their usage limits.
The builds aren't notarized by Apple or code-signed for Windows yet. The app's own updates are signed and verified, and the source is on GitHub.