Murph - local agent for async handoffs in Slack and Discord Murph, a local-first handoff agent, allows users to maintain async continuity in Slack and Discord by monitoring selected channels, drafting replies, and applying user-defined policies while they are offline. The tool stores runtime state locally via SQLite and local credentials, giving indie developers, founders, and distributed teams control over what gets sent, queued, or skipped with a full review trail. Murph integrates with tools like Notion, GitHub, and Google Calendar, and supports OpenAI and Anthropic LLM providers for grounded, context-aware responses. Murph is a local-first handoff agent for the hours you are away. Start a session before you log off. Murph watches the channels you choose, pulls context from connected integrations and tools, drafts grounded replies, applies your policy, and leaves a review trail for every decision. | What you need | What Murph does | |---|---| Stay offline without losing momentum | Watches selected messenger channels while you are away | Keep control explicit | Sends safe work, queues risky work, and skips anything it should not answer | Use your real context | Pulls from docs, tickets, email, calendar, meetings, GitHub, and local notes | Review what happened | Shows what was sent, queued, skipped, and why | Run it yourself | Stores runtime state locally with SQLite and local credentials | Murph is built for people who want async continuity without handing over control: indie developers, founders, operators, and distributed teams. Install Murph: curl -fsSL https://murph-agent.com/install.sh | bash Run setup: murph setup Start Murph: murph start Check your local install any time: murph doctor Return to a clean local slate: murph uninstall --dry-run murph uninstall | Topic | What's covered | |---|---| | Installation https://murph-agent.com/docs/installation Configuration https://murph-agent.com/docs/configuration Policy https://murph-agent.com/docs/policy Usage https://murph-agent.com/docs/usage murph , the browser UI, and murph agent for setup, sessions, review, and daily operation. Plugins https://murph-agent.com/docs/plugins Channels https://murph-agent.com/docs/channels Integrations https://murph-agent.com/docs/integrations Core Concepts https://murph-agent.com/docs/core-concepts Contributing https://murph-agent.com/docs/contributing Murph includes a local coding agent for setup, debugging, policy changes, and scoped integration work. murph agent Use it to connect services, inspect setup issues, and create scoped plugins without editing Murph core. By default, it can write plugin and configuration files; source edits require an explicit --source-edits flag. Learn more in Murph Agent https://murph-agent.com/docs/usage/murph-agent . | Category | Options | |---|---| | Channels | Slack, Discord + any channel of your choice | | LLM providers | OpenAI, Anthropic | | Integrations | Notion, GitHub, Gmail, Google Calendar, Granola, Obsidian + custom plugins | | Tools | web search, web fetch, file read, shell + custom tools | | Storage | SQLite + local file system | Read CONTRIBUTING.md /dannylee1020/murph/blob/main/CONTRIBUTING.md before opening a pull request. Keep changes focused, include validation, and update docs for user-facing behavior. Murph is organized around a few extension points: Channels for messaging surfaces. Integrations for connected external work sources. Plugins for local extensions. Skills for request-specific behavior. Tools for individual callable actions. Policies for autonomy and review rules. Providers for model backends. The listed integrations and tools are defaults, not a closed set. Custom integrations and tools should start as scoped plugins before changing Murph core. For local development: npm install npm run dev npm test Open an issue before starting non-trivial core/runtime changes. Apache 2.0