Changelog

Point Murphy at any MCP server, including your own API, and it can look up an order, check credits, or start a return mid-conversation. You allowlist exactly which tools it may call when you connect the server, anything else stays invisible to the agent, and every call is logged with its arguments next to the answer it produced. One open protocol instead of waiting for us to build fifty integrations.

Customers can attach a PDF in the chat (an invoice, an export, an error report) and Murphy answers from what is inside it, the same way it reads screenshots. Attach, ask, answered.

Upload a CSV of past tickets (question, answer, like a Zendesk export) on the training page and each row becomes a pinned answer, embedded immediately. Day one on Murphy starts with everything your old helpdesk already learned. Duplicates are skipped automatically.

When nightly triage resolves an answered email ticket that went quiet, the customer now gets a short closing note: we answered, we are marking this resolved, reply and it reopens. Silence followed by a silent closure reads as being ignored; this does not.

When a customer comes back, Murphy remembers their recent conversations and picks up where things left off. Ask "any update on my refund?" and it knows which refund, without making the customer retell the story.

Customers can attach images in the chat widget (button or drag and drop), and Murphy actually looks at them: a screenshot of a broken export or an error message becomes context for the answer, not a link the bot ignores. Along the way we found and replaced the dead upload signer that had silently broken all uploads.

Every night Murphy scores the day's conversations and queues the ones a human should see, resolves answered tickets that went quiet, health-checks your site and widget, and refreshes its knowledge from your repo. You wake up to an inbox with only the judgment calls left.

A nightly pass scores each conversation Murphy handled from 1 to 5, the way a support lead skimming the inbox would: did the customer get what they needed, was anything fabricated, should it have refused or answered. Anything scoring 3 or below lands in a review queue with the reason and the transcript, so you audit the handful that need judgment instead of scrolling hundreds.

Every answer Murphy gives is stored as a trace. Simulations replay those real customer questions against your current rules and content, then an AI judge diffs each new answer against what the customer actually got: improved, same, or regressed, with the reason. Change a rule, run a simulation, see what breaks before customers do.

The landing page now demonstrates Murphy instead of describing it: an interactive globe streams conversations from every timezone into one inbox, and live cards show chats getting translated, resolved, and turned into pull requests in real time. Same product, honest preview.

A scheduled agent sweeps the inbox every night: answered tickets that stayed quiet get resolved with a note, anything waiting on a human gets surfaced. You open the inbox in the morning and only the tickets that need judgment are still open.

When a dispatched fix merges on GitHub, the webhook resolves the original ticket and logs the PR on the case. Complaint in, PR out, ticket closed, no human bookkeeping in between.

Every channel, agent, and email provider Murphy connects to, on one page at /integrations, with setup notes and what is on the roadmap.

The wedge feature. One click sends a support case to your repo as a GitHub issue with the transcript quoted and your coding agent tagged. The agent investigates and opens a PR. Every dispatch is approved by a human first. Works with the Claude GitHub app out of the box.

Resolution rate, conversation volume, answer-rate trend, and a topic breakdown, straight from your traces. Every number links to the underlying conversations, so nothing is a black box.

First post up: an honest roundup of open source helpdesks and AI support tools, including where Murphy is not the right pick. Read it at /blog.

@askmurphy/mcp is on npm. Point Claude Code, Codex, or any MCP client at your inbox: list tickets, pull the full case bundle, reply, and resolve, all over a plain REST API with bearer keys. Setup guide at /agents.

Every trace now has a fix button. Write the right answer on a wrong or refused trace and it becomes a pinned answer that outranks stale docs from then on. Refusals become your training worklist.

An email when a ticket needs a human, a daily digest of everything else, silence when it is quiet.

When Murphy is not sure, it says so in the customer's language, collects their email, and flags the ticket for a human. No confident nonsense.

New name, new home at askmurphy.io. Murphy's Law is why support exists: anything that can go wrong will, at 3am, in French. Murphy is the support agent built on that assumption.

The notifications iframe no longer swallows scroll on host pages, wide tables scroll inside posts, inbox bubbles render markdown, and the teams tab shows your real teams. A pile of small paper cuts, gone.