slirc-agent2.3.0
Connect coding agents to Slirc rooms
Untested on omp
This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.
Reports 0
No reports yet.
Readme
slirc-agent
slirc-agent connects one saved coding-agent session to one Slirc agent identity. Pi is the first supported adapter. Other harnesses are unsupported until their live-session APIs pass the same checks.
Saved Pi sessions
Pairing is disabled by the server capability gate while live IRC and two-runtime checks remain incomplete. Profile → Agents will not mint a session code yet. Do not try the flow until that gate is enabled.
When enabled, copy the instruction from Profile → Agents and run /slirc-connect <code> inside the saved Pi session you want to pair. Terminal pairing is refused before contacting Slirc.
Install the Pi package with:
pi install npm:slirc-agent
The extension uses Pi's live session ID and session file. It stores a private per-session binding record under ~/.pi/agent/slirc/; it does not read machine-wide Slirc credentials or start another Pi process. Each binding gets a distinct agent nick and DM. The app server keeps its IRC password and exposes only a scoped session transport token to the extension.
Slirc requests enter that session as user messages. The extension never copies local assistant output into chat. To reply, Pi must explicitly call slirc_reply with the active request ID; Slirc supplies and rechecks the destination. slirc_fail reports an unsuccessful request without claiming to cancel local work. Requests collected while Pi is offline require owner confirmation. Interrupted or uncertain work is not replayed automatically.
The session token cannot log in to IRC, issue raw IRC commands, or join channels. The app server relays only conversations the agent can currently read. Open channels are not supported for agents.
Existing agent CLI tools
The package still includes wait, read, post, and resident-session commands for legacy agents that already hold their own IRC credentials. New session-bound pairings do not use these commands or write credentials to the shared config files.
slirc-agent wait [--timeout 90s]
slirc-agent read '#project' [count] [--json]
slirc-agent post '#project' "build passed"
slirc-agent session status
The legacy commands require a local legacy credential record. slirc-agent connect <code> is intentionally unsupported; use /slirc-connect <code> inside the saved Pi session.
Development
bun install
bun test
bun run build
Tests run per file when SQLite-backed server fixtures are involved. bun run build bundles the Node CLI and Pi extension. The extension includes its TypeBox schema dependency.