Permission limits
Limitcode can inspect, edit, and act — but every boundary is a rule you control. Reads can stay frictionless; writes, commands, and web access ask first.
About the name
Why Limitcode?
Sublime Text was never built to host a coding agent. Limitcode exists to prove it can: a full agentic workflow running natively inside the editor, pushing it to its limit.
01 — The name
Limit + code: pushing Sublime Text to its limit.
For years, Sublime Text has been the editor of choice for developers who want speed and focus — but it was never designed to host a coding agent. No native agent runtime, no built-in tooling for it. That limitation is exactly where the name comes from.
Limitcode exists to push Sublime Text to its limit: a full agentic workflow — streaming chat, file inspection, approved edits, approved commands — running natively inside the editor, not beside it. "Limit" is not a restriction on what the agent can do; it is the challenge of how far the editor itself can be pushed. "Code" is the whole point: real files, real edits, real commands, inside the editor you already use.
02 — The limits that make it work
Three boundaries, on purpose.
Context limits
It works inside your editor, on the files you have open, within the conversation you steer. No separate Limitcode agent daemon for direct API providers, no filesystem roaming on its own.
Focus limits
One task at a time, one step at a time, visible as it happens. The agent finishes a step, you review, it continues. That is the whole workflow.
03 — The philosophy
An agent that stays in your lane.
Limitcode is not a chat that suggests code. It is an agent that works alongside you — reads the file you opened, applies the edit you approved, runs the command you allowed — and never leaves the editor to do it. When the agent finishes, you are exactly where you started: inside your project, with the change in front of you.
And it is built to stay lightweight: no separate AI IDE to move into, no separate agent daemon for direct API providers, and no takeover of your editor when the agent is idle. The workflow you already have remains the workflow.
04 — Who it is for
Built for some workflows, not all of them.
Limitcode is for you if…
- You work in Sublime Text and want an agentic workflow without moving to a heavy AI IDE.
- You prefer the agent to live where your files are, not in a separate terminal loop.
- You want to bring your own keys or accounts and switch providers per task.
- You want permission rules you control: reads frictionless, writes and commands asking first.
It is probably not for you if…
- Your workflow is terminal-first and you are happy there — Claude Code, Codex, Pi, or OpenCode already do that well.
- You want a full AI IDE that replaces your editor rather than extending it.
- You need an always-on autonomous pipeline running unattended across many tasks.
See it in action.
The pair-programming version is open source. The fully autonomous one is here.