Threads
One conversation, many repositories.
A thread is a conversation with no repository of its own. Give it a goal and it starts a session on each repository that needs a change, then follows each one until the work is done.
- Starts a session on each repository the goal touches
- Hears when a session finishes, opens a PR or needs an answer
- Stops when its sessions stop making progress
- Every session it starts is one you can open and steer
Threads use box-hours like sessions do. There is no separate limit on threads.
Usage billing rollout
ThreadThat touches three repositories. I am starting a session on each.
The web session asks whether usage should round to whole hours. The API returns seconds.
Reply to the thread.
Sessions of this thread
Usage API client
sundial/apiPR open
Usage page
sundial/webNeeds an answer
Billing docs
sundial/docsWorking
Repositories of this thread
sundial/api
sundial/web
sundial/docs
When one change is three pull requests
A new API field needs the server, the client and the docs. That is three repositories, three branches and three agents, and somebody has to keep them in step.
A thread does that part. You describe the goal once. It works out which repositories need a change and starts a session on each.
Usage billing rollout
ThreadThat touches three repositories. I am starting a session on each.
The web session asks whether usage should round to whole hours. The API returns seconds.
Reply to the thread.
Sessions of this thread
Usage API client
sundial/apiPR open
Usage page
sundial/webNeeds an answer
Billing docs
sundial/docsWorking
Repositories of this thread
sundial/api
sundial/web
sundial/docs
It keeps track for you
Each session tells the thread when it starts, finishes a turn, opens a pull request or needs an answer. Most of these give the thread's agent a turn, so it can react: answer a question, or start the next step.
When it needs you, it says so in the thread, with a link to the session.
It knows when to stop
If its sessions make no progress between two of its turns, the thread stops waking itself and waits for you. It does not spin on a stuck problem all night.
Step in any time
Every session a thread starts is an ordinary session. Open it to read the diff, run the tests in its terminal or send it a message yourself. The thread's side panel lists its sessions and repositories.
Questions, answered.
A session is one task on one branch of one repository. A thread has no repository. It starts sessions on the repositories a goal needs and follows them.
On the new session page, choose New thread, describe the goal and press Enter.
A thread and its sessions use box-hours while their sandboxes are awake, like any other session. The model runs on your own subscription.
Talyn does this for you.
Coding agents in cloud sandboxes, from the first prompt to the merged pull request, on the Claude or ChatGPT plan you already pay for. Free with 10 box-hours a month.