Factory Droid

Factory Droid sessions in your Mac notch

Every droid run visible, flagged the moment it waits, and resumable from the composer.

Download for FreeFree 3-day trial · Apple silicon

01

Droid, out of the terminal shadows

Run droid in a terminal (or work in the Factory desktop app) and the session appears in the notch with live state, current activity, tool calls on the timeline, and subagents under their parent. Turn completions flip the state where you can see it, with notifications when you're looking elsewhere.

02

Approvals: flagged instantly, answered natively

Factory keeps approval decisions in its own surface, so AgentPeek doesn't intercept them. What it does is make sure you notice: a Droid session waiting on an approval is flagged for attention the moment it blocks, the notch can auto-expand, and ⌥ T jumps you to the session. The composer sends follow-up prompts into resumable Droid sessions once they're waiting or idle.

03

Setup and routes

Hooks install into ~/.factory/settings.json, with Doctor repair, and Quick Routes opens the Factory config and project logs. Droid exposes no usage data AgentPeek can read yet, so its sessions appear without usage numbers.

Questions, answered.

Yes. Droid sessions from the CLI or the Factory desktop app appear in the Mac notch with live state, tool activity, and subagents, and follow-up prompts go into resumable sessions from the composer.
No. Factory keeps approvals in its own surface, so AgentPeek flags the waiting session for attention, can auto-expand the notch, and jumps you to the session with Option T instead of answering for you.
Yes. Droid sessions that carry a resumable session ID accept follow-up prompts from the notch composer once the session is waiting or idle, with the reply streaming into the session card.

Your agents, one glance away.

Download for FreeFree 3-day trial · Apple silicon