For Codex, Claude Code, and other coding agents

# An ambient *interrupt channel*

Coding agents are powerful, but they receive human state only when the developer deliberately sends another turn. Presence lets them notice what matters while the work continues.

[Try Presence free](https://presence.bohita.com/?try=1) [See a real session](https://presence.bohita.com/coding-agents#workflow)

THE OPERATING PRINCIPLE

Know enough about the person I am working with to choose the right moment to listen, speak, act, or stay quiet.

One recorded run

## It saw the error. Then helped fix it

Presence was not told about Clerk, the bug, or the fix. It noticed the pause and offered to look. The developer then asked it to inspect the shared window.

01:12.949

Presence offers to take a look.

03:57.117

The developer asks it to inspect the open window.

+184 ms

A fresh shared-window frame arrives.

+7.038 s

Analysis identifies the excluded dashboard route.

[See the full run](https://presence.bohita.com/evidence/clerk-auth-evidence-v1.txt)

42 second excerpt. The transcript includes complete timing, the disclosed edit, and the machine-readable event sequence.

1. 01
Presence was told to check in when the developer seemed stuck.
2. 02
The developer hesitated during a Clerk authentication test.
3. 03
Presence checked in and offered to inspect the shared window.
4. 04
The developer pointed to the open error and asked it to look.
5. 05
Presence captured a fresh frame and identified the matcher exclusion.
6. 06
It gave the precise fix. The developer confirmed that it worked.

REAL TEAMS SESSION · 05:13 PROACTIVE CHECK-IN 184 MS FRAME RECEIPT **No typed bug report**

Keep every tool

## Add the channel that is missing

Presence is not a substitute for structured access. It removes the requirement that every meaningful human state change be serialized into a new prompt.

Codex still wants

- Repository
- Terminal
- Tests
- Browser and DOM
- Logs
- Tools

Presence adds

- Human state
- Visual context
- Ambient events
- Attention cues
- Initiative

Ambient in both directions

## The agent notices you. You can read the agent

The face is not decoration. Expression and attention provide a low-bandwidth indication of state without forcing either side to stop and explain it.

Image: Human and agent exchange speech, expression, attention cues, and artifacts while tools continue asynchronously

Following Noticed something Thinking Confused Reacting

Where it earns its place

## Useful between prompts

There is no universal list of moments that matter. The agent's instructions define what to look for. Presence carries those moments into the working loop while tools continue.

You test what it built **It can notice that something changed or did not work**

You are debugging visually **It can react to the error or shared surface you are looking at**

A long task is still running **It stays available without making you manufacture another prompt**

You step away or return **It can stop expecting an answer, then know when the work can resume**

You react without saying anything **It can offer help when that reaction is relevant to what you asked it to notice**

For a one-shot file edit, Presence adds little. It matters when the work includes testing, waiting, reacting, and showing.

Evaluate it honestly

## Keep the coding agent you already trust

Give it the repository, terminal, tests, browser, logs, and tools it needs. Then evaluate whether adding human state creates useful interventions that could not happen through those tools alone.

THE TEST

Can the agent choose a better moment to listen, speak, act, or stay quiet without the developer manufacturing another prompt?

Two ways to start

## Try the ambient loop. Then give the install to your agent

[Try Presence free](https://presence.bohita.com/?try=1) [Get an API key](https://presence.bohita.com/account/api-keys) [Read llms.txt](https://presence.bohita.com/llms.txt)