Task notifications now bound the title (internal/app/archied/outcome_post.go notificationTitle), and task_spawn caps new titles at 80 runes. The on-demand chat listings do not: /tasks renders each title raw in internal/gateway/gateway.go formatTasks, and /agents does the same in handleAgents. A task from another writer (issue, schedule, pre-cap chat task) still produces an unreadable line there. Done when both listings bound the title the way notificationTitle does, without dropping the task ID.
Imported from beads archie-core-4z6ep · GitHub #1890 · type bug · priority P2 · created 2026-10-26
Task notifications now bound the title (internal/app/archied/outcome_post.go notificationTitle), and task_spawn caps new titles at 80 runes. The on-demand chat listings do not: /tasks renders each title raw in internal/gateway/gateway.go formatTasks, and /agents does the same in handleAgents. A task from another writer (issue, schedule, pre-cap chat task) still produces an unreadable line there. Done when both listings bound the title the way notificationTitle does, without dropping the task ID.
---
_Imported from beads `archie-core-4z6ep` · GitHub #1890 · type bug · priority P2 · created 2026-10-26_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Task notifications now bound the title (internal/app/archied/outcome_post.go notificationTitle), and task_spawn caps new titles at 80 runes. The on-demand chat listings do not: /tasks renders each title raw in internal/gateway/gateway.go formatTasks, and /agents does the same in handleAgents. A task from another writer (issue, schedule, pre-cap chat task) still produces an unreadable line there. Done when both listings bound the title the way notificationTitle does, without dropping the task ID.
Imported from beads
archie-core-4z6ep· GitHub #1890 · type bug · priority P2 · created 2026-10-26Fixed in
48c28b36b, on main and deployed.