Many agents write your code.One helps you decide where to look.

All your Claude Code and Codex sessions in one window. AIDE's own agent puts the one that needs you in front.

Join the waitlist See how it decides In design, not released. macOS first.

A simulation of the AIDE window with five coding-agent sessions. It opens on four terminals side by side and the line "Nothing needs you". One session then stops at a permission prompt, and its terminal grows to the front while the others stack beside it. The Layout manager's line under the tabs says what it moved and why, with Keep and Undo buttons. A ranked list on the left shows the sessions that need you.

Layout manager Nothing needs you4 working, showing all four

Rate limiter for /searchsearch-api · feat/rate-limit · Claude Code

> add a token-bucket limiter to /search, 20 requests a second per key

● Update(src/middleware/limit.ts)

⎿ Added 41 lines

● Update(src/middleware/limit.test.ts)

⎿ Added 68 lines

● Bash(npm test -- limit)

⎿ 12 passed

✳ Wiring the limiter into the router… (41s · esc to interrupt)

● The limiter works. One question before I wire it in: should a limited request keep the current JSON error body, or switch to problem+json?

Migrate orders tableorders-service · migrate/orders-v2 · Claude Code

> move orders to the v2 schema on dev, then backfill order_items

● Read(migrations/014_orders_v2.sql)

⎿ Read 58 lines

● The migration adds two columns and one index. I'll run it on the dev database first.

✳ Checking the dev database… (9s · esc to interrupt)

Bash command

psql $DEV_DB -f migrations/014_orders_v2.sql

Run the orders v2 migration on the dev database

Do you want to proceed?

❯ 1. Yes

2. Yes, and don't ask again for psql commands

3. No, and tell Claude what to do differently

● Bash(psql $DEV_DB -f migrations/014_orders_v2.sql)

⎿ ALTER TABLE, CREATE INDEX: 3 statements ok

✳ Backfilling order_items… (12s · esc to interrupt)

Bench: image resizemedia-worker · bench/resize · Codex

› benchmark resize at 256, 512 and 1024 px and write a report

• Explored

└ Read bench/resize.mjs, src/resize.ts

• Ran node bench/resize.mjs --sizes 256,512,1024

└ 3 runs complete

• Added reports/latency-report.html (+212)

• Working (38s · esc to interrupt)

Upgrade to Node 22web · chore/node-22 · Codex

› upgrade the web app to Node 22 and fix what breaks

• Edited .nvmrc, package.json (+3 -3)

• Ran npm ci

└ installed, no errors

• Ran npm test

└ 2 failed, 318 passed

• Working (1m 04s · esc to interrupt)

Peeklatency-report.htmlmade by Bench: image resize · v3 of 3

Latency report reports/latency-report.html

3sizes compared

2.7 msbest p50

3.6 msbest p95

256 px2.7

512 px3.9

1024 px6.8

What it shows

Resize time grows with the pixel count. 1024 px costs about two and a half times 256 px, and no size has a slow tail.

How it was measured

node bench/resize.mjs, three runs per size, warm cache, one worker.

Sample sessions. Try Keep and Undo.

An agent whose only job is your attention.

It writes no code. It watches your sessions and does three things.

1 of 3

It ranks what is important.

Blocked first, then whoever waited longest. Working sessions stay out of the way.

Twelve sessions. Which one needs you?

2 of 3

It chooses what you see.

The window follows the list. Or just say how you want it.

Layout manager

Try “show everything” or “rate limiter in front”.

3 of 3

It suggests the next step. You decide.

One line, one keystroke to undo. It never steals focus.

Layout manager Next: Rate limiter for /searchwaiting 6m, asks a question

What it does

Puts the session that needs you in front
Opens new reports beside their session
Offers the next session when you finish one

What it never does

Take keyboard focus
Move the pane you are typing in
Move anything once you switch it off

And the basics, done right.

Sessions that survive

Close the window or restart. Every session picks up where it stopped.

Peek at what agents made

Reports an agent writes open beside the session that wrote them.

Usage you can trust

Tokens per session, and when you'll hit your limit.

Light on memory

Native, not a browser per tab. Hidden views sleep and wake as you left them.

Your CLI, untouched.

A window around the tools you already use.

The real CLI in every tab
Unmodified, in a real terminal.
Your logins stay yours
AIDE never sees your tokens.
No sign-up
Pick a folder and go.
No telemetry
Only the update check leaves your machine.

reposearch-apibranchfeat/rate-limitharnessClaude Codemodelopusaccountwork

✻ Welcome to Claude Code!

/help for help

cwd: ~/code/search-api