A year of building a terminal IDE without writing code: 50 releases, 2,573 commits, and what the agents needed A developer built termide, a Rust terminal workspace with a file manager, editor, terminal, git and agent panel, entirely through AI coding agents over a year, reaching version 0.50.0 on November 16, 2026, with 2,573 commits and roughly 215k lines of Rust plus 88k lines of tests. The developer reports that the core agent instructions barely changed, while most additions to the public AGENTS.md addressed validation and coordination, including rules against `git add -A` after agents staged other sessions' work. The developer also notes that throughput rose sharply with spare subscriptions, hitting 675 commits in October, which is when parallel-session conflicts piled up. Disclosure. This article was drafted by an AI coding agent from my answers and from the project's git history and session logs. I checked every fact and number in it. It belongs to the experiment it describes. A year ago I started termide https://github.com/termide/termide , a terminal workspace in Rust: file manager, editor, terminal, git and an agent panel, laid out in panels. It had two goals from the first day: I have not written any of its code by hand. Version 0.50.0 came out on November 16, 2026. The repository holds 2,573 commits and about 215k lines of Rust code plus 88k lines of tests. Below is what I learned. My main conclusion: the method I described to the agent in the first days hardly changed all year. What kept growing was everything around it: checking that the agent really did what it said, and keeping several agents from getting in each other's way. In the first days I described to the agent how I see the stack and how I work on a project. It went into a private CLAUDE.md , which is gone now. In April it became the public AGENTS.md , my description with the agents' edits. Compare the April version with today's: it grew from 80 to 104 lines. Every section was already there in April: sources of truth, language policy, commit discipline, architecture constraints, anti-patterns, validation, documentation. In seven months exactly one section was added, Parallel sessions and worktrees . Every other change is about validation. So the "how we work" part of the rules was settled early. Everything new has the same two causes, and both are below. My main tool all year was Claude Code. I also use it at work, which matters more than it sounds. I tried Codex, pi, OpenCode, Gemini CLI, Qwen Code and jcode, along with OpenAI, GLM and Kimi subscriptions and DeepSeek and Qwen models. None of them took over. On my tasks they were usually slower or closed fewer tasks well, though now and then one of them pulled ahead for a while. This is my impression from daily work, not a benchmark. The experiments came from frustration. Every so often the model I depended on became noticeably dumber and less careful, with no warning. Or the subscription limit ran out in the middle of a task. Then I either waited for the reset or opened a new session in another harness. That is why CLAUDE.md became AGENTS.md in April: the rules had to be readable by whatever harness I switched to. Today CLAUDE.md is only a symlink to AGENTS.md , and the skills moved from .claude/skills to a shared .agents/skills . Rules tied to one vendor bind you to that vendor's bad week. Throughput mattered more than I expected. In September and October I had more spare subscriptions than usual. Commits went from 40–200 a month to 391 in September and 675 in October, with the same rules and the same person. That was also when the problems below piled up. Most of the process was mine and local from the start, the pre-commit hook included. It went into the repository when someone besides me needed it: another harness, or a second parallel session. Each item below has a commit or a session log behind it. Parallel sessions sweeping up each other's work. Several agents worked in the same checkout at once. On October 7 an agent staged a whole file and took in two lines another session had written there. The hook rejected the commit because those lines didn't compile without the rest of that other work. On October 14 an agent ran git add -A and staged two finished files from another session. Only an unrelated clippy failure stopped that commit. Its own reasoning, from the log: These changes are NOT mine… someone else is editing concurrently… I must NOT commit their work into my commit. It noticed only after staging them. The rule now in AGENTS.md : stage by explicit path, never git add -A , check git diff --cached --stat before a commit and git show --stat HEAD after. A shared build directory. Worktrees that shared one CARGO TARGET DIR overwrote each other's artifacts. Clippy in the hook took about 4 minutes instead of 24 seconds while another worktree was building. On October 29 target/ was 341 GiB . Cargo never collects old artifacts, and nobody had looked. Now each checkout has its own target directory, and the hook warns past 40 GiB. A merge that silently dropped changelog entries. On October 15, resolving a conflict in CHANGELOG.md kept one branch's entries and lost three from the other commit 5334829f , "restore the plan-mode MCP entries a merge dropped" . Each change now writes its own file under changelog.d/ , and the release folds them together. Parallel branches never edit the same lines, so a merge has nothing to drop. Unused dependencies. Cargo doesn't warn about a dependency you declare and never use. By September 99 of them had piled up across the workspace. cargo machete now runs in the hook and in CI. "Done" that wasn't. This was the expensive one. A simple check over the history: take a feat x commit and see whether a fix x follows within three days. | Period | feat commits | followed by a fix in the same scope within 3 days | |---|---|---| | Dec 2025 – Feb 2026 | 82 | 18% | | Mar – Jun 2026 | 174 | 51% | | Sep 2026 | 170 | 72% | | Oct 2026 | 213 | 83% | | Nov 1–17, 2026 | 59 | 58% | The heuristic is rough. A fix in the same scope isn't always a fix of that feature, and busy scopes match by chance more often. Still, the trend is clear: more throughput and more parallel sessions brought more rework. In November an agent ran a read-only audit of the development process. It found that UI features were "checked live" with throwaway scripts in /tmp , and that the process rules lived in one agent's private memory, not in the repository. Two things came of it. First, tools/tui-harness : it runs the built binary headlessly against scenario scripts, with a throwaway home directory and a mock model, and AGENTS.md now requires it for UI and agent changes. Second, the rules moved from private memory into AGENTS.md . November's lower number covers only part of a month, so I wouldn't call it a result yet. By then the hook already mirrored CI, and since September it checked the staged tree rather than the working tree. Otherwise it judged code that wasn't the code being committed. In September termide got its own agent panel. All my work now happens there, not in a terminal panel with Claude Code. Limits were one reason. The main ones were different: /prompt shows the assembled prompt exactly as the model gets it screenshot below . For scale, measured the same way with tokei code lines without blanks, comments or tests : | | Language | Code | Tests | |---|---|---|---| | termide agent 8 agent- crates + panel | Rust | 49k | 38k | | pi coding-agent and its in-repo dependencies | TypeScript | 116k | 144k | | jcode | Rust | 546k | 335k | | all of termide, agent included | Rust | 215k | 88k | This is not a like-for-like comparison. termide's agent runs on the editor, terminal and widgets the rest of termide already has, and those aren't counted in its row. The last row is for scale: the whole workspace, file manager, editor, terminal, git, database and diff panels and the agent together, is still less than half the size of jcode. pi's number includes its own TUI library. Rust and TypeScript lines don't compare one to one. Running into a limit now looks like this. The panel reads the reset time: from the API's Retry-After , from what the Claude Code adapter reports, or from text like "resets 9:50pm" for Codex and Gemini CLI. A card offers Wait until 21:50 and try again . While the card is open I can switch the session to a spare subscription or to a local model in the status bar and press Try again now . The conversation continues where it stopped. If the failed turn had already called tools, the agent is told to carry on, so nothing runs twice. What's still open is the question my own panel was built for: how small can a system prompt be before quality drops? I don't have the answer yet. My next step is to run termide's agent on Terminal-Bench against other harnesses with the same local model. termide is open source MIT : github.com/termide/termide https://github.com/termide/termide . Questions and criticism are welcome here or in r/termide https://www.reddit.com/r/termide/ .