About Riby
A pager for AI agents.
Riby reaches you when an agent hits a decision it should not make alone. You answer from Telegram, Discord, or the dashboard. The agent keeps its place and carries on with your answer.
Human time, not machine time
A request waits for six hours by default. That is long enough to leave your desk, eat lunch, or sleep. If you do not answer, Riby denies the request. No answer never becomes silent permission.
Blocking that holds
Riby runs as a local stdio MCP server. It keeps the call alive while your agent waits, so a page is a real pause in the work rather than a notification that arrives after the agent has moved on.
Requests survive the process
Each request is written to an append-only ledger on your device. The agent can crash. The laptop can sleep. When the agent resumes, the answer or safe expiry is still there.
Built by one developer
Riby is built and operated by Sivaram, an independent developer. It stays narrow on purpose: one tool, pager-sized requests, and a dependable way to answer the decisions that matter.