Maintainer of this skill?
# Add to your Claude Code skills
git clone https://github.com/nodecode-ai/nodecodeSee how nodecode compares with popular alternatives.
nodecode is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by nodecode-ai. A living agent organism in Lisp. It has 159 GitHub stars.
nodecode's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/nodecode-ai/nodecode" and add it to your Claude Code skills directory (see the Installation section above).
nodecode is primarily written in Common Lisp. It is open-source under nodecode-ai on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh nodecode against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Nodecode is an agent that rewrites itself. It runs as one process in SBCL, a Common Lisp system, and shells attach to it. The model has one tool: it evaluates Lisp in the running program and keeps what it defines.
Linux and macOS:
curl -fsSL https://nodecode.ai/install.sh | sh
Windows, in PowerShell:
irm https://nodecode.ai/install.ps1 | iex
Then run nodecode. The first launch opens setup. If another coding agent lives on the machine (Claude Code, Codex, Hermes Agent, OpenCode, Cursor CLI, Gemini CLI and 9 more), setup names it and asks before it reads anything; say Import and it brings over the agent's keys, instructions, memory, skills, MCP servers, bots and jobs, tick the agents one by one when it found several, or Skip and /import brings them over later. Then you pick a provider, a model and the reasoning effort. See Quickstart and First run.
An orchid opens new flowers while it keeps growing. An installed Nodecode updates itself the same way: most releases go live in the running program, one changed definition at a time, with no restart. Its own growth is kept as generations: nodecode generations lists them, nodecode rollback N restores one, and --pristine runs the binary alone. Updates
A cell is a folder that teaches Nodecode something new: a chat room it can live in, a provider login, a tool, a skill, a GitHub repo, an MCP server. nodecode add nc://cline installs one from the hub and turns it on in every attached shell. Or ask Nodecode to write one. Cells
Like an organism, Nodecode decides what stays in its context and what goes, and nothing it lets go is lost. Old turns leave the window whole, never rewritten into a summary; (recall-entry N) reads any of them back word for word, and /evict makes room when you ask. The idea behind Context Language Models (Shao et al., 2026). Context and recall
"Its programs are in the same format as its data." (John McCarthy, 1984). Code is data, so a program can rewrite itself while it runs. The model's one tool, eval, evaluates Lisp in the running Nodecode: what it defines runs at once and is kept, one file per definition, committed with git, loaded at every start. Missing a tool? It writes one. Eval and the layer
The gateway is the local server every client attaches to: the terminal, a browser tab (nodecode web), your phone (/link on), bots in Discord, Telegram and Slack, and programs (nodecode rpc). They all talk to the same running Nodecode, so a tool it writes in one is there in all of them.
On Linux and macOS the background gateway is on by default: it keeps Nodecode running with no shell open and starts it at login. nodecode gateway shows its state. On Windows, keep nodecode serve open in a terminal. See The gateway.
To put it in a chat room:
nodecode gateway setup discord # or telegram, slack
It walks one channel from the bot's token to a connected bot. The token stays in a private file or an environment variable, never in the config, and the bot answers only the channels and people you allow.
On the same model, Nodecode won every public ARC-AGI-3 game with 54% fewer tokens than Claude Code (41% less cost) and 66% fewer tokens than the Codex CLI (24% less cost). The write-up: What ARC-AGI-3 costs, Foresight Labs FL-2026-006.
The 25 public ARC-AGI-3 games, 183 levels, each scored with the official scorecard rule, all harnesses at xhigh reasoning. A token is every token put through the model: input, cache reads, cache writes and output. Cost uses each provider's official prices of 11 October 2026. Where a game was played more than once, the best run counts, for every harness alike. On Claude Opus 5.5, Nodecode and Claude Code both score 100. On GPT-6.1 Sol, both win all 25 games; the Codex CLI, playing through Prime Intellect's published game adapter, scores 99.9 to Nodecode's 99.5 because it took fewer actions. The GPT-6.1 Sol runs reached the model through a LiteLLM gateway and a third-party API relay.
Turn one on with Space in /cells, or `nodecode