Chats, issues and goals
SoduWork has three ways to start work. They all end up in a chat, where you follow the agent's progress.
| Way | Use it when | What is recorded |
|---|---|---|
| Chat | You want an answer or a quick job now | The conversation and its files |
| Goal | The work should keep going until it's done | A goal with checkpoints, kept on the chat |
| Issue | The work needs criteria, an owner, review or collaboration | A record on the Hub with its own history |
Issues
An issue holds the goal, background, completion criteria, owner and materials. The main path is:
collect the issue → assign it to yourself, a colleague or AI → follow up in its chat → review the delivery
- The Issues board has columns for inbox, Not started, In progress, Awaiting acceptance and Done. It can be grouped by project or owner; a list and a Gantt view share the same filters. Archived issues are shown separately.
- Execution and acceptance states come from the Hub. An AI reply doesn't mean the issue is done.
- Several issues in the same project can share one long-running project chat, keeping its harness (runtime), model, working folder and context. Each turn still records which issue it belongs to.
- Materials, history, collaboration records and delivery review stay in the issue's panel.
In the API and database, an issue is a Task. That's the internal name; there is only one record, with one set of attachments, approvals, comments and deliveries.
Assigning work
When you choose Assign issue, you can pick an existing project chat or start a new one. Issues that aren't ready, are archived, read-only or already running can't be dispatched again.
A plugin workflow can run on an issue. Its approvals and acceptance are controlled by the Hub (Workflow nodes).
Goals
Choose Set a goal to let the agent keep working toward a goal across turns. Harnesses that declare native goal support run it with their own goal mode.
harness harnesses runtime runtimes 底座