Agents as Unix commands.

$ ai 'What am I in the middle of? One line.'
assistant: I can't tell. I don't have access to your terminal, files, or session history, only what you've typed here, so tell me what you're working on and I'll help from there.
$ clai -asc git q 'What am I in the middle of? One line.'
assistant: You're on `fix/rate-limit` with uncommitted edits to `api/api.go` and `limiter.go`, following up on your "fixed-window limiter" commit (`f660a40`).
$ ▌

$ for p in security perf style; do git diff | clai -p $p -r q 'One line.' > $p.txt & done; wait
$ cat security.txt perf.txt style.txt
security: Allow now discards the Store.Incr error, so if the backing store fails (n likely 0) the rate limiter fails open and lets every request through, which allows attackers to bypass limits (e.g., brute-force protection) by triggering store outages; restore the error return or explicitly fail closed.
perf: swallowed store error in Allow means failed increments are treated as n=0 and silently allow unlimited requests, losing all rate limiting on store outages.
style: Don’t ignore the Store.Incr error (`n, _ :=`); return/wrap it, since swallowing it can turn backend failures into false allows/denies and makes debugging impossible.
$ ▌

$ cat limiter.go | clai -i q 'Name the bug in one line: {}'
assistant: **Bug:** `Allow` discards the error from `Store.Incr` (`n, _ :=`), so a store failure returns `n == 0` and the limiter silently fails open, allowing every request.

Fix: check and return the error (or deliberately choose fail-open or fail-closed):

```go
n, err := l.Store.Incr(key, l.Now().Truncate(l.Window))
if err != nil {
        return err
}
if n > l.Max {
        return ErrLimited
}
return nil
```
$ ask -cm claude-haiku-5-5 'Now the smallest fix, two lines max.'
assistant: ```go
n, err := l.Store.Incr(key, l.Now().Truncate(l.Window))
if err != nil { return err }
```
$ ▌

$ ai 'We answer rate-limited calls with 429 and Retry-After. Acknowledge in one line.'
assistant: Understood: rate-limited requests get an HTTP `429 Too Many Requests` response with a `Retry-After` header telling clients when to retry.
~/work/web $ ai 'Pick a toast library for a small Go web app, one line.'
assistant: **Notyf** is a tiny, dependency-free JS toast library that works well with server-rendered Go templates (trigger it via flash messages or htmx `HX-Trigger` headers).
$ ask 'What did we decide here? One line.'
assistant: We decided that rate-limited calls get a `429 Too Many Requests` response with a `Retry-After` header.
$ ▌

$ clai -t generate_image q 'A minimal orange triangle on a dark navy background.'
assistant
  {"prompt": "A minimal orange triangle centered on a dark navy backgrou
  nd. Flat vector style, clean edges, no other elements.", "rebus": "🔶
  🌙 📐", "size": "1024x1024"}
▸ generate_image  prompt=A minimal orange triangle centered on a dark n…
  ▸ [🔶 🌙 📐] image 4d0420 · gpt-image-2.5-flare · 1024×1024 (1:1) · 842 KB · 6s
  → file:///tmp/clai-site-demo/home/.config/.clai/conversations/assets/4d042013f5e3cafa56c6132749372d0bab1cebc948b595b8fde562d3a597b84b.png

assistant: I generated the image: a flat orange triangle centered on a dark navy background, with nothing else in it.

It's saved at `/tmp/clai-site-demo/home/.config/.clai/conversations/assets/4d042013f5e3cafa56c6132749372d0bab1cebc948b595b8fde562d3a597b84b.png`.
$ clai -re q 'One line: what did you draw?'
assistant: A flat orange triangle, centered on a dark navy background.
$ ▌

$ curl -fsSL 'https://www.clai.chat/hub/<slug>/raw' \
-o "$(clai confdir)/profiles/reviewer.json"
$ clai -p reviewer q "One line: what should a caller do when tx.Commit() fails?"▌
Treat transaction outcome unknown; rollback, retry idempotently, reconcile externally.