WeSearch

Murph - local agent for async handoffs in Slack and Discord

·2 min read · 0 reactions · 0 comments · 36 views
Murph - local agent for async handoffs in Slack and Discord
TL;DR · WeSearch summary

Murph is a local-first handoff agent designed to maintain productivity during offline hours. It monitors selected messaging channels, pulls context from various integrations, and drafts responses while ensuring user control over what is sent. The tool is particularly beneficial for indie developers, founders, and distributed teams seeking asynchronous continuity without losing oversight.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
GitHub
Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGitHub
Canonical URLhttps://github.com/dannylee1020/murph
Publication timeMon, 25 May 2026 21:18:44 +0000
Retrieval time2026-05-25T21:37:40.575Z
Last seen2026-05-25T21:37:40.575Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterZsEt8gFsE61F
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Murph 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…

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub