Loki
Chat with your own PC. A local Slack agent running on your Claude Code subscription — no API key.
Mention it in Slack and it does the thing on the machine sitting under your desk. Discord runs on the same core.
No API key. It runs on a Claude Code subscription, which means the cost model is a flat monthly fee instead of per-token billing — the difference that makes leaving an agent running all day actually viable. It’s a public repo, and someone running a fork once sent me three bugs with diagnoses and patches attached.
Written up in four parts
| The problem | |
|---|---|
| Architecture | Swapping both the platform and the brain while keeping one core |
| Commands | How much you can actually ask for through a chat box |
| Permissions and guards | Opening an agent with shell access on your own PC to other people |
| Silent failures | Almost every bug returned success and did nothing |
What it’s actually used for
Long-running pipelines that outlive a chat session. Kick off a test-case run from a phone, get the report back in the thread hours later. The PC does the work; Slack is just the handle.
And one more — a session on another machine posts to Slack as me, and the Loki on this PC runs it. That story lives under silent failures, because it’s a feature that came out of fixing a bug.