ljos runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 14 Oct 2026.
Local memory, a work tracker and a shell-command guard shared by coding agents on one machine.
What the code does
We read the source, 2 d ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const proc = Bun.spawn([LJOS, "hook"], {
for (const key of Object.keys(process.env)) {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to ljos
same job, measured the same wayShared, git-tracked working memory for AI agents on the same codebase.
Local-first governed MCP memory backend for coding agents.
Local-first governed MCP memory backend for coding agents.
Local-first long-term memory for AI coding agents. Stored on your own machine.
Shared memory MCP server for AI coding agents — local by default, team-shared via threadctx.dev.
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
One shared, durable memory for your AI coding agents — local-first, zero-dependency.
Shared memory for parallel AI coding agents. Local, free, with rooms and file claims.
ljos — questions
Answers built from our own checks of this server.