Salaam is a persistent session service for agent work, built on Pi. sal service start runs a service on my machine or an execution host, and the terminal, SSH and ACP-speaking editors all attach to the same sessions. I can close the terminal, come back later, and find the same session, tasks, approvals and results.
The README puts the problem in three sentences I agree with: closing a client should not discard an agent’s session, reconnecting should not submit the same instruction again, and an agent saying “done” should not be the only evidence that a task succeeded. Salaam is the lab’s own harness, and AgentPod is adding it as a first-class station alongside the third-party harnesses it already manages.
How it works:
- A pinned Pi worker owns the conversation. Salaam owns the durable task and operation records.
- Tasks have checked plans, budgets and checkpoints, and model text cannot mark a checked task complete.
- Coding is opt-in. Each proposed edit or command is reviewed before it runs.
- If the daemon dies, dispatched attempts are interrupted and never silently replayed.
- The default provider is offline, so a first session needs no API key and makes no paid request.
It is early software, meant for one trusted OS account. Its Unix sockets don’t isolate hostile programs running as that same user, there is no public multi-tenant API, and request and token limits are not a spend cap. It runs on macOS and Linux; Windows is not tested.