# What should an agent be allowed to do with what it overhears?

OverhearOps: Use-case design, Python. Repository created Sep 2025.
Code: https://github.com/jlov7/OverhearOps
Page: https://jasonlovell.ai/projects/overhearops

An R&D system that overhears team chat and drafts dry-run fixes.

## Design choice

It drafts but ships nothing by default: side effects run only in live mode with an approver's sign-off, and an uncertainty gate refuses to ship when confidence is low.

## In practice

An agent that listens in on a team should draft, not act. Keep its side effects behind a dry-run default and a named approver.

## What I built

- Detects actionable threads in Teams-shaped conversations and drafts plans, down to a PR diff and a Jira stub
- Plan branches with a judge that picks one; replay regenerates the decisions and checks a stored hash
- Dry-run by default: live shipping needs an approver's sign-off
- OpenTelemetry traces, action graphs and a governance view with trace IDs and the replay hash

## Where it stops

A personal R&D system built to run locally. By default it replays two Teams-shaped demo threads with deterministic model fixtures; the Microsoft Graph adapter needs tenant credentials, and live model calls need a provider key. Its guard blocked every attack in its own 8x5 prompt-injection suite, which says nothing about attacks outside that suite.

---
By Jason Lovell. Independent work, separate from my role at PwC.