About
Somcode is two people who got tired of babysitting an agent that kept editing the wrong file, and decided to build the one we actually wanted.
We both work on large, unglamorous codebases. The assistants we tried were good at producing plausible code and bad at understanding the project it had to live in. They would rewrite a helper that already existed, miss the caller three directories away, and report success on a test suite that was already failing before they started.
So we built the opposite: index the repository properly, show the plan before touching anything, and treat your own test command as the only acceptable definition of done. It is deliberately unexciting to watch.
The two of us
R. Vance
Indexing and retrieval - the part that decides which file to open before a single token is spent.
K. Ibarra
The planning loop, test integration, and the terminal interface you stare at all day.
What we optimise for
- The agent should be boring We would rather ship a diff you can review in a minute than a demo that looks impressive and needs an hour of cleanup.
- Green tests or it did not happen Somcode is not allowed to claim success on a failing suite. The test command is the gate, not a suggestion.
- Your repository stays yours Local index, local history, no telemetry, and a model endpoint you choose.
Contact
Bug reports, beta requests, procurement questions, or a plain disagreement
about how the plan step should work:
hello@somcode.fmys.dev
We usually reply within two working days. This site is served from the same machine we develop on, which is either charming or a warning sign.