Skip to content
Threadbear
What it does How it works FAQ Docs
Get Threadbear
  • Home
  • What it does
  • How it works
  • FAQ
  • Docs
  • Get Threadbear
Using Threadbear
  1. Threads
  2. Full access or Ask before edits
  3. Your first thread
  4. Hibernate and archive
  5. Panels
  6. Highlights
  7. Schedules
  8. Accounts, pools and Usage
  9. Connectors
  10. The prompts macOS shows you
  11. Your phone and a browser
  12. Patches: your own buttons and panels
  13. Changing Threadbear itself
  14. Privacy
  15. Getting help
  16. The tour and Finish setting up

Schedules

A schedule sends a message at a set time, once or over and over: to a thread, or to a new thread each time (a morning summary, say). Make one in the Scheduled view (⌘2), or ask an agent ("look at this again every weekday at 9"). The Scheduled view lists them with when each runs next, and its page says what's coming up next with a few numbers: how many are on, due in the next day, repeating, set by threads, paused, and how often they've run.

If you run Threadbear on more than one Mac, a schedule that starts a new thread can run on any of them: pick the Mac under Runs on. It runs there even while this one is asleep, in that Mac's folder (leave the folder empty for its default). Its threads show on your phone and the website, and threads made on another Mac show in your sidebar too, with that Mac's icon in the row: open one and you're talking to that Mac directly (over Tailscale), so it needs that Mac to be on and its key copied to this one. Pictures and files in them stay on that Mac for now. Schedules need your Convex backend: with no internet, they wait.

Next: Accounts, pools and Usage

Threadbear is made by Mike Cann. It runs the official Claude Code and Codex command line tools, and isn't made by or connected to Anthropic or OpenAI.

Home How it works FAQ Docs Help Privacy mikecann.app