Repository navigation
Kyoube apps can now hand work to your agents. A person presses a button in an app, the right agent gets a task, and the app shows the agent's reply and the data it updated.
What's in 1.9.0
Task templates. An app declares the tasks it can send: which agent, a title, instructions with the row's and the person's values filled in, and the fields the agent may write back. A person confirms these when publishing a version that adds or changes a template, or that would send it to a different agent. An agent can't publish that version or roll back to it. A published version keeps the agents it was confirmed with, so renaming agents doesn't redirect anything.
Started by people, as themselves. Only people start or cancel tasks, and the task is created in their name. The core's own assignment rules apply, so someone who may not assign a protected agent is refused inside an app too. An agent is only asked to write Data the person can write.
Follow it to the end. The app watches the task as it goes from waiting to working to done (or needs review, blocked or cancelled). It shows the agent's reply and re-reads the rows the agent changed. It can open the task page or cancel the task. If an agent is paused, or the core won't wake it (for example when it is over budget), the start fails with a clear reason, so no task is left stranded.
Kept in bounds. App data reaches the agent in a fenced block marked as data, with size limits. Limits apply per app: 10 templates, 10 starts a minute per person and 25 open tasks. Every start and cancel is audited without row values. Company Settings → Data access lists each template, its agent and whether that agent can write Data.
Update
From 1.8, run ./update.sh. It backs up first, and ./update.sh --rollback returns to 1.8. The update adds one empty table and changes nothing until a person publishes an app version with task templates.
How app tasks work, and what they don't cover, is in docs/app-tasks.md. The full list of changes is in CHANGELOG.md.