A complete, batteries-included GNU Emacs distribution built for AI-assisted Lisp development: SLIME, paredit, magit, org-mode, and a status dashboard, native-compiled and preconfigured. In every mode it carries a built-in MCP endpoint through which any MCP-capable agent — Claude Desktop, Claude Code, Cursor, Gemini CLI, Codex — works alongside you in the same running Emacs.
The prevailing custom embeds one AI agent inside one editor. Readymacs inverts that: the environment embeds no agent, and *receives* them instead — any client connects from outside, and the running Emacs joins the visiting agent's toolkit, under your supervision.
The modes are independent and each idempotent — all three can coexist on one machine.
The recommended mode: Readymacs is the console of a Basalt deployment — Emacs, Gendl engines, and monitoring come up together with one command, and your host stays clean apart from the shell convenience commands for reaching the containerized Emacs.
One `docker/run` from a clone: the Emacs daemon running, the MCP endpoint listening, your ~/projects mounted. No deployment, no other services — the container is the sandbox.
`./setup` links the configuration into your own account for your own Emacs. MCP stays OFF by default in this mode — on a host, `lisp_eval` is arbitrary code execution and the containerized modes are the sandboxed path. Read the docs before enabling it.
Agents connect through Lisply-MCP and receive `lisp_eval`, `ping_lisp`, documentation lookup, HTTP access, and document-corpus search. Understand the boundary before enabling anything: the lisply endpoints themselves, not the wrapper in front of them, are the security surface — in a container that is the point, and on a bare host it is why they ship disabled.