What AI can do
AI in UTSUROI is not just a chat window. It can actually read and write your boards and tasks.
Three surfaces
Section titled “Three surfaces”There are three ways AI reaches UTSUROI, and all three use the same set of tools. What differs is whether a write needs your approval.
| Surface | Where | Reads | Writes |
|---|---|---|---|
| In-app AI chat | The Agent button, top right | direct | approve and run |
| Slack AI | Mentions and reactions in Slack | direct | needs approval |
| MCP | External AI tools like Claude Code | direct | runs directly |
What it can do
Section titled “What it can do”Across all three surfaces:
Read
- Boards, lanes, labels, projects and members
- Task search, your own tasks, tasks due or overdue
- Recent activity, and per-task history
Write (approved, or run directly)
- Create tasks — one, many, or recurring
- Update title, description, dates, project and size
- Change lane, parent and ordering
- Change assignees, the ball holder, and labels
- Add comments, create labels and projects
- Archive and restore
Per-tool arguments are in the tool reference.
What it deliberately cannot do
Section titled “What it deliberately cannot do”- Physical deletion. Archiving works, and archived tasks can be restored
- Lane-wide bulk mutation
These are simply not offered, so that an AI cannot do anything irreversible.
Roles and scopes
Section titled “Roles and scopes”Permissions come in two layers.
- Role — viewers and guests cannot write on any surface. Raising a token’s scopes changes nothing
- Scope — MCP narrows further with
mcp:tasks.read/mcp:tasks.write/mcp:boards.settings
A workspace in a restricted state (over the Free limit, say) is read-only too.
Where to start
Section titled “Where to start”- Never tried it → the in-app AI chat. No setup, works right now
- Want to know what pays off → AI recipes
- Want to drive it from your own AI tool → Connecting MCP