# Session examples — OneCue

> OneCue is the decision layer for coding agents. It surfaces the recorded decisions that bear on the task — what was chosen, why, and what each rules out — right before your agent changes the code. Usually one, a few when the task spans several, each with its source, or silence. Local-first: OneCue’s store never leaves your machine, though your coding agent’s own model provider still sees your code.

See what carries forward. Not the entire conversation — the decision that
changes what your agent does next. These are scripted illustrations of the
local skill, not live agent runs or measured benchmarks.

## Dead end avoided — "Make the queue faster."

Saved earlier: `decision · queue-storage — Keep Postgres SKIP LOCKED. Redis
reconnects duplicated queued jobs.`

Without OneCue, the agent reads queue-worker.ts, finds no Redis usage, proposes
moving the queue to Redis, and has to re-derive why it was rejected. With
OneCue, the prompt surfaces the prior decision (match 0.81) and the agent
proceeds with tuning SKIP LOCKED batch size instead.

## Rejected approach recovered — "Improve failed checkout recovery."

Saved earlier: `dead end · booking-retries — Client retries duplicated
bookings. Recovery stays server-side.`

Without OneCue, the code shows a retry but not that client retries already
failed; the agent rebuilds a browser retry loop and duplicates bookings in
staging. With OneCue, the cue (match 0.74) keeps recovery server-side.

## Silence for unrelated work — "Rename the settings button."

No saved record applies. OneCue judges the prompt, surfaces nothing, and the
agent works as usual. Silence is a feature: the store is not dumped into every
prompt.

Next: [Install OneCue](https://onecue.sh/install)