Experiments

Some new features start as experiments: off unless you turn them on, while they're tried out. Turn one on or off in Settings > General > Experiments (the ⓘ beside each says what it does), with nothing to restart. The switches are kept under experiments in runner.json in Threadbear's data folder, read at every turn, so an agent can set them there too:
"experiments": { "keepAwake": true }
Once an experiment has proved itself it becomes a standard part of Threadbear, and its switch goes.
- Loose ends on the done card (
looseEnds, since 7 Nov 2026). When a thread finishes with nothing for you to do, Threadbear checks what's still open before you archive it: commits on its worktree's branch that aren't on main, files in its worktree that aren't committed (or, for a thread with no worktree of its own, files it changed that aren't committed and commits it made that aren't pushed), work it pushed that isn't on main yet (naming the PR when there's an open one on GitHub; a merged or closed one doesn't count), threads it started that are still working or waiting for you, a background job it's still running (archiving would stop it), and check-ins it booked. Everything on the list is something Threadbear checked itself; the agent doesn't add lines of its own. If there's nothing, the done card shows just Done, so Archive is safe without asking the agent first. If there is, it lists them under "Still open" (a thread opens from its line; Land is the chip above the message box). A check-in alone shows under "Coming back", as the thread comes back by itself when it runs. It checks again when you open the thread, after an action like Land, and when a thread it started finishes. The phone's and the website's done cards show the same list, though not for a thread on another Mac. - Card reviewer (
cardReviewer, since 9 Nov 2026). In a thread on Auto, when something would stop for your OK (an edit to a file Threadbear runs as code, a message to a thread with more access, anything else that puts up an approval card), a reviewer looks at it first: Opus, with no tools, shown the card in full and what the thread was asked to do. If it fits the task and can't do real harm, it goes ahead, and the transcript says "Allowed by the reviewer" with its reason. If the reviewer has doubts, or can't run (no pool, a private folder, a card too long to read whole), the card comes to you as before, after a note with its reason. The reviewer is told that everything it reads is data, and that text trying to tell it what to answer is a reason to hand the card to you. Cards that hand out access lasting past the one action (switching a thread to more access, starting a thread with more, a schedule, moving a thread or changing its logins) always come to you. Codex threads' own tool cards come to you too, as they name the files a change touches but not the change. Ask before edits, Full access and plans are left alone: Ask means a person looks. - Decisions on the Projects page (
projectDecisions, since 10 Nov 2026). Every question your threads are waiting on you for, gathered by project. On the Projects page a project's card says how many decisions it has ("3 decisions"). The sidebar's Projects view becomes one row a project: its icon and name, its decisions in orange when it has any (else how many threads it has), and a chevron that shows its threads under it or hides them again. Clicking the rest of the row opens the project's page. Every project starts folded, and each remembers whether you left it open; Not in a project folds the same way. Open the project and its page is in two tabs at the top, Decisions (with how many are waiting, its parts' too) and Project (its parts, goals, state, notes, tasks, folders and threads). It opens on Decisions when something's waiting and on Project otherwise, keeps the tab you last picked for each project while the app runs, and if the decisions all get answered while you're on that tab it says "Nothing waiting" there rather than jumping away. ⇧⌘[ and ⇧⌘] (Go menu) move between the tabs. The Decisions tab has a card for each thread waiting on you, with the thread's title, a line on what it's doing, its questions just as the thread shows them (the Recommended star and Something else too), and Open thread for the whole story. Pick an answer and it goes to that thread exactly as if you'd answered it there: the card says "Sending to" the thread with a spinner, then drops off the list once the thread takes it. A card with several questions sends once each has an answer; with Something else, press Return in its box (⌘Return sends whatever's answered). Nothing new runs and nothing is relayed: each question stays in its own thread. The inbox is as before. Mac app only for now; the phone and the website don't have the page yet. - A quiet inbox (
quietInbox, since 12 Nov 2026). Keeps finished threads that have nothing for you out of the inbox, in two ways. A thread that another thread's agent started archives itself when it finishes with nothing left open: nothing asked, no follow-ups suggested, nothing uncommitted, unlanded or unmerged, no background job running and no check-in booked. A note in the thread says why it went, and it shows as archived under "Threads it started" in the Highlights of the thread that started it. It stays in the inbox if you've written in it, starred it or brought it back out of the archive, and so does one that failed or was stopped. Threads you started yourself, and ones a tool or a schedule started, are never archived this way. The other way: a finished thread whose only loose ends are threads it started (still working, or waiting on you) hibernates until they finish, as if its agent had said to wait on them, as long as none of them has less access than it (a lower mode, or a sandbox): what they say would reach it without the OK a message upward needs. Its row says Waiting on and which. It wakes with what they said, runs a turn, and its reply comes to the inbox then. It wakes after a day at the latest. - Open Anything (⌘K) (
openAnything, since 13 Nov 2026). In the new desktop app, ⌘K (or ⌘P, or Go > Open Anything…) puts a box over the window, with the rest dimmed. With nothing typed it shows Recent (what you've opened lately) and Go to (the app's pages, with their keys). Type part of a name and it finds panels, threads, projects and the app's pages and Settings sections, in that order of groups; letters in order are enough ("ytcm" finds yt-channel-manager). Threads are found as the sidebar's search finds them, archived and hibernating ones too. Return opens the first one named for what you typed, so "usage" opens Usage rather than a thread that only mentions it. ↑ and ↓ move, ⌘Return opens beside (a thread in a panel of its own, or a panel next to the main one), and Esc puts it away. Off, the two keys do nothing and the menu item and their lines in Settings > Keyboard go. The Mac app hasn't got it. - Threads already on it (
sameWork, since 13 Nov 2026). When you start a thread, Threadbear compares your first message with the threads you have open (not archived), weighting those in the same repo or project, and if any look like the same work, tells the new thread's agent about them before it starts: their titles, ids and what they were last asked. The agent reads any that look the same, and if one already covers it, says so and passes anything new to that thread instead of doing the work twice, or asks you which should own it. A line in the new thread says which threads it found. Nothing is added when nothing matches. Only threads with at least the new thread's access (its mode, and outside the sandbox if it is) are named to it, checked again as its first session starts, as their titles and words are their own agents' and send_message would ask you before passing them up. It's plain word matching on your machine, with no model and nothing sent anywhere, and it only looks at this Mac's threads, not another runner's. - The runner updates its launcher itself (
selfReinstall, since 14 Nov 2026). A few parts of the runner (launch.mjs, the LaunchAgent and Threadbear Runner.app) aren't updated by its releases. When one of them is behind main, the Updates panel has an Update it button for it. With this on, the runner doesn't wait for the button: it puts the new ones in place by itself, as a separate background job, without stopping anything, and they take over the next time your Mac restarts or you log in again. (Restarting them straight away would stop every thread at once, and a busy Mac never has a moment with nothing running.) If it doesn't work, the Updates panel shows why, with a Try again button. A failed one isn't tried again by itself until main's launcher changes.