Agent Session Library
Node.js client for the agentd socket, plus a small demo window and a simulated test-driven-development runner.
packages/robos-agent-session
robos-agent-session is mainly a library. Its window exists to demonstrate the API.
The library
index.js exports RobOSAgentSession, AutonomousEDDRunner and EDD_PHASES. RobOSAgentSession talks to Agent Daemon over the Unix socket ~/.config/robos/agentd/agentd.sock (override with the socketPath option). If the socket is missing, calls resolve to { ok: false, error: "Socket not found at ..." }. You can also pass an in-process daemon object to skip the socket.
| Method | What it sends |
|---|---|
spawnAgentSession(taskId, options) |
spawn |
listAgentSessions() |
list; returns an array |
inspectAgentSession(taskId) |
inspect |
sendAgentCommand(taskId, command) |
appendLog with the line [COMMAND_DISPATCH] <command>. It records the command in the session log; it does not execute it. |
terminateAgentSession(taskId) |
terminate |
wipeAllSessions() |
wipeAll |
runEDD(config) |
Runs the local EDD runner (below). |
The object is an EventEmitter and emits session:spawned, session:command, session:terminated and session:wiped.
The EDD runner
lib/edd-runner.js steps through the phases ingestion, red verification, implementation, green verification, regression check and completed, and logs each one. The red and green checks are simulated: the runner returns fixed results and only calls fabric.dispatchRequest if you pass a fabric object. Treat it as a scaffold for the phase model, not a test runner. Knowledge Graph Explorer loads it.
The demo window
main.js opens RobOS Agent Session Client Demo. It starts its own in-process agent daemon, so it does not need robos-agentd to be running. The window has + Spawn via Library, Refresh and Send Command controls, a session list and an event log. There is no .desktop launcher.
Tests
npm test in the package runs node --test.
More in Agent Services & MCP Servers
Agent Autoconfig
Writes MCP configuration and instruction files so Claude Code, Gemini, Copilot and Cursor all point at the RobOS MCP router.
Agent Daemon (agentd)
Keeps a registry of sub-agent sessions, each with its own home directory and environment, behind a Unix socket and a small window.
Agent Profile Daemon
Creates short-lived agent profiles with their own home directory (tmpfs when run as root) and runs commands with that home and environment.
CI Monitor MCP Server
An MCP server that lets agents list Buildkite builds and read failed-job logs, backed by the connection set up in CI Monitor.
Dev Tools MCP Server
An MCP server with a small catalog of developer CLI tools; "install" and "check" read and write a JSON file and do not touch the system.
Engineering Knowledge Graph MCP Server
An MCP server that lets agents search and edit a small node store, query and propose changes to the SDLC graph, and look up schema types.
IDE Bridge MCP Server
An MCP server that forwards IDE commands (open file, breakpoints, run configurations, refactorings) to the RobOS IntelliJ plugin on port 63343.
MCP Router
Single MCP endpoint that lists the tools of the servers in the registry and routes tool calls to them, with built-in fallbacks.
MCP Server Framework
Node.js library for building small Model Context Protocol servers, with an HTTP and a stdio transport and a shared registry file.
RobOS CLI Tools
Four shell scripts for scripts and agents: send a notification, set the active task, append to the work journal, and emit or read events.
System MCP Server
MCP server with six tools for preferences, notifications, a tool inventory, file-name search and the active task, backed by a JSON file with sample data.
Task Manager MCP Server
MCP server with seven tools for listing, creating and advancing tasks stored in ~/.config/robos/tasks/tasks.json.
Workspace Manager MCP Server
MCP server with six workspace tools, backed by a JSON file of sample workspaces. Several tools return canned results and do not run anything.