Threads
Work with the agent in a conversation that keeps the context and history of a piece of work.
A thread is a conversation with the Continual agent. Use it to build an app, investigate a problem, work through a decision, or carry out an operation. Messages, tool activity, and results stay together so you can continue the work later.
Start a piece of work
Describe the result you want, provide relevant files or context, and explain any constraints. A useful request names what should change and how you will judge the result.
A thread belongs to a project and works on a branch. That context determines the source and runtime it uses. Check the project and branch when work depends on an existing app or database.
Continue the conversation
Reply in the same thread to clarify a request, review a result, or ask for a revision. Start another thread for a separate piece of work. You can rename a thread to make it easier to find and archive it when you no longer need it in your active list.
Questions and results
The agent may ask for information while it works. Durable requests appear as tasks, where you can read the context and provide a response. A thread can also contain app previews and links to the resources it used or created.
Review the result against your request. A completed response tells you what the agent did; it does not by itself prove that an external action succeeded or that an app is ready for production.
Repeat work with an automation
Use an automation when the same instructions should run on a schedule or in response to events. An automation can start separate threads or continue in a persistent thread.