2026-07-30

Daily AI Digest: WorkBuddy co-writes; voice agents answer

This is the GolemWorkers Daily AI Digest for July 30, with five practical agent developments for work, customer service, health care, security and long-running projects. WorkBuddy brought selective co-editing into everyday documents, while Dave and Emily showed support agents moving from chat to verified transactions and pharmacy tasks.

An operator reviews documents, a headset and a protected project binder at a calm work desk.
Two colleagues review selected sections of reports, spreadsheets and presentation pages together.

WorkBuddy edits only the part of a document you select

Tencent WorkBuddy 5.3.5 added “Human-Agent Dual Writing” with Tencent Docs. A user can select part of a Word, Excel, PowerPoint or Markdown file and ask the agent to revise that region while preserving the surrounding content and formatting; the workflow supports both local Office files and cloud documents.

Source: Pandaily
A marketplace support team reviews a complex customer case during a busy product launch.

G2A gives marketplace sellers a 24/7 support agent

G2A globally launched Dave after a 63-day deployment in which the company says the agent helped handle about 15,000 tickets and reduced cases requiring human support by 27–30 percent. Dave works across 180 countries and checks transaction history, payment status and seller policies before answering or routing a case.

Source: TechRound via TechnologyNewswire
A patient makes a phone call while collecting a refill at a bright community pharmacy.

MUSC’s voice agent now handles routine pharmacy calls

MUSC Health expanded its SoundHound-built voice agent Emily into retail and specialty pharmacy phone lines after using it across more than 2.2 million patient calls since 2024. Patients can request refills, hear real-time status updates, check pharmacy hours and locations, or be routed to a pharmacy team for needs that require people.

Source: SoundHound AI
A security engineer supervises a sealed credential handoff across an isolated network boundary.

Infisical lets agents use credentials they never receive

Infisical made Agent Proxy generally available on every plan, including its free tier. Agents send placeholder credentials through the proxy, which applies the real secret at the network boundary before forwarding the request; Infisical says the approach works with standard HTTP clients, CLIs and MCP servers without placing live credentials inside the agent.

Source: Infisical via PRWeb
A records specialist archives evidence beside customer-controlled storage and a separate locked credential case.

AIStor Memory keeps long-running agent work under customer control

MinIO launched AIStor Memory as a customer-controlled persistence layer for agents that need to resume work across sessions. The product separates durable decisions and evidence, active workspace files and protected credentials while keeping them on the customer’s AIStor infrastructure; MinIO positions it for research, engineering and human-in-the-loop work that spans hours or days.

Source: MinIO

Agent idea of the day

Build a security-alert briefing agent that remembers resolved cases

Two security engineers compare a new alert packet with prior case evidence before approving a response.

What this agent does

Turn each new security alert into a source-linked briefing that compares recent resolved incidents, gathers the relevant audit evidence and leaves the final response with the on-call engineer.

Best for: Security and IT operations teams that already receive alerts in tools such as Slack, Asana or a SIEM and keep useful resolution notes.

Give it

  • A read-only alert feed and an approved set of audit-log queries
  • Resolved incident notes with human conclusions and source links
  • Your escalation rules, expected maintenance windows and the actions that always require approval

Tell it to

  1. Read the new alert, identify its actors, systems and time window, and do not change its severity.
  2. Retrieve the most recent resolved cases with matching signals and prioritize cases that contain a human investigation conclusion.
  3. Run only the approved read-only queries needed to confirm or contradict the apparent match.
  4. Assemble an evidence brief with source links, conflicts, missing facts and a confidence-limited recommendation.
  5. Ask the on-call engineer before downgrading an alert, opening a pull request, changing a rule or contacting anyone.

Run it: Run whenever a new alert arrives and produce a combined handoff summary at each shift change.

You get

A compact alert packet containing the likely match, evidence timeline, unresolved questions, recommended next step and explicit approval requests.

Keep a human in control

  • Keep investigation tools read-only by default and scope each tool to the smallest necessary dataset.
  • Never treat a similar past incident as proof that the current alert is benign.
  • Link every conclusion to the alert, log result or human note that supports it.
  • Require a human decision before any external message, severity change, code change or access-policy mutation.

Feasibility: Figma describes a production workflow that indexes prior alert investigations, retrieves recent human conclusions, and routes scoped agents to tools such as Okta, Panther, Wiz and read-only audit data. Its retrieval layer reduced on-call pages by 20 percent in the reported deployment, while higher-impact actions such as code changes remain visible to engineers through pull requests and explicit tool boundaries. Source: Figma →

GolemWorkers — OpenClaw ready to work: launch in seconds, no setup, online 24/7.