Show HN: Nodecode, open-source living agent in Lisp that rewrites itself for you
Hi HN, we're Mike and Thom. Agents of the future should only have one tool (the interpreter, ideally a LISP eval), nothing more or less; to interact with the world. Agents remember by writing markdown files. NODECODE remembers by rewriting itself. And that is in itself a new paradigm in working with agents. What if memories, skills, MCPs, provider connectors, tools, etc. all live under the same image as *.lisp files instead of in disarray across random folders? Ask it for something it can’t do,
Read original source
Source record
Recorded metrics
points · 3 votes
2026-10-26 18:00:30.153Z
cumulative since publication
Research analysis
Project record
Repository: nodecode-ai/nodecode. Source account: Hi HN, we're Mike and Thom. Agents of the future should only have one tool (the interpreter, ideally a LISP eval), nothing more or less; to interact with the world. Agents remember by writing markdown files. NODECODE remembers by rewriting itself. And that is in itself a new paradigm in working with agents. What if memories, skills, MCPs, provider connectors, tools, etc. all live under the same image as *.lisp files instead of in disarray across random folders? Ask it for something it can’t do,
Observed adoption & comparisons
Source votes: 3 votes (Oct 26, 2026 UTC; cumulative since publication); previous same-scope observation: 2 (Oct 26, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “Show HN: Cerea – yet another self-hosted LLM chat front end” (Show HN, Nov 5, 2026); “Show HN: Lantern Lattice – the call graph from your compiler, for coding agents” (Show HN, Nov 5, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.