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

Full access or Ask before edits

Read this before your first thread. Every thread runs in one of two modes, shown on the composer (the box you type in) and changed by clicking it.

  • Full access (the default): the agent edits files and runs commands without asking. It can do anything your Mac user account can do, in any folder, including deleting files. This is how Threadbear is meant to be used day to day, and it's fine for a folder you trust it with.
  • Ask before edits: the agent stops for your OK before it edits a file or runs a command. A card shows in the thread with Allow, Always allow and Deny. Always allow only lasts for that thread. A Codex thread in this mode can read files but not change them unless you agree.

The mode belongs to one thread. A new thread starts on Full access again unless you pick otherwise, so if you're unsure about a task, switch it to Ask before edits before you send. Deleting a thread is one thing an agent always has to ask about, whatever the mode.

Next: Your first thread

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