Are these greys the same?
From ask to done, right on your Mac.
Twigs lives in the notch. Ask in text, speak, or highlight what you're working on. It moves the work across your apps, then checks the result before it says done.
Ask in text, out loud,
or by pointing.
Ask, right where you are.
Tap ⌥ twice and a box opens at your cursor. Ask about what you're working on, or start a Run from the same place.
Hold a key and talk.
Hold ⌃⌥, say what you need, let go. It answers out loud, and you can talk over it.
Point at part of your screen.
Hold ⌃⇧ and drag a box around anything. Twigs works from just that, and nothing else.
Your day,
handled.
Traced it to line 142. Patched, re-ran. Tests green.
Acceptance criteria included.
Follow-up email drafted and ready.
Weekly recap
Numbers double-checked.
How Twigs works: ask, act, speak
The answer was
never the job.
Most assistants stop at the reply. Twigs keeps going, and checks itself before it stops. The rules below are the whole product.
- 01
Do the work.
A reply isn't the job. Finishing is.
- 02
Earn the check.
It checks its own work before it says done. No green check it didn't earn.
- 03
Stay out of the way.
It lives in the notch. There's no new window to manage.
- 04
Only what you show it.
It keeps up with what you're working on. The rest, it never touches.
- 05
One ask, every app.
It does the work across your apps. No copy. No paste.
Built for people who'd rather it were done than discussed.
The tenth Run
knows more than the first.
It keeps what you've shown it and carries it from one Run to the next.
You explain it once. Every other assistant starts over every time.
It stays on your machine.
Your memory is stored on your Mac, never uploaded, never shared.
Yours to clear.
Wipe your memory whenever you want. It forgets on command.
It won’t say it’s done
until it’s actually checked.
Every Run ends with an outcome: done, unverified, halted, cancelled, or failed. If Twigs cannot prove the work landed, it says so.
You're in control.
Twigs works across your Mac the way you would. It stays in the open, asks before anything it can't take back, and keeps a record of every move. Nothing happens behind your back.
In the open
It acts in front of you, never off somewhere you can't see.
Asks first
Delete, send, overwrite. Anything it can't take back, it checks with you.
Every action logged
A full record of what it did, and when. Yours to read any time.
It only knows
what you show it.
You choose the context. Blocked places never enter a Run: password managers, terminals, banks, iMessage, and FaceTime stay outside the gate. Not a setting you turn on. The way it's built.
Password managers
1Password, Bitwarden, and saved secrets stay outside the gate.
Banks and terminals
Your bank and every terminal are blocked by construction.
iMessage and FaceTime
Private Apple conversations stay outside every Run.
Works where
you work.
A Run can file the Linear issue, update Notion, send the Slack handoff, or open the GitHub issue. Results don't get stuck in a chat box.