Hermes version: v0.13.0 (2026.5.7)
Component: Kanban board (hermes_cli/kanban_db.py)
Problem
When using a project-specific kanban board (e.g. a board for the "chieftain" / ng-land project), every task creation requires manually setting . There's no way to configure a board-level default workdir so all tasks on that board automatically inherit the project's root directory.
Currently:
- Tasks have an optional column
- Every task must have set explicitly at creation time
- Workers pick up from the task record and pass it via
- No board-level fallback exists
Impact
For users with project-specific boards, this creates repetitive manual work. It's error-prone — a forgotten means the agent operates from the wrong directory, picks up wrong AGENTS.md/CLAUDE.md, and uses wrong context for file/terminal operations.
Suggested Fix
Add a board-level configuration for default workdir:
- Add a column to the table (or a JSON column)
- When a task is created on a board that has set, automatically populate on the new task if not explicitly provided
- When a worker picks up a task with no explicit , fall back to the board's
- CLI:
- CLI: to see current settings
Use Case
User has a board for the ng-land (chieftain) project at . They want every task on that board to automatically use that workdir without having to specify it each time. Setting it once at the board level means all future task creations inherit it.
Alternative Considered
A skill-based workaround (add task creation skill that auto-populates workdir) is possible but puts the burden on the user rather than solving it natively in the kanban system.
Hermes version: v0.13.0 (2026.5.7)
Component: Kanban board (hermes_cli/kanban_db.py)
Problem
When using a project-specific kanban board (e.g. a board for the "chieftain" / ng-land project), every task creation requires manually setting . There's no way to configure a board-level default workdir so all tasks on that board automatically inherit the project's root directory.
Currently:
Impact
For users with project-specific boards, this creates repetitive manual work. It's error-prone — a forgotten means the agent operates from the wrong directory, picks up wrong AGENTS.md/CLAUDE.md, and uses wrong context for file/terminal operations.
Suggested Fix
Add a board-level configuration for default workdir:
Use Case
User has a board for the ng-land (chieftain) project at . They want every task on that board to automatically use that workdir without having to specify it each time. Setting it once at the board level means all future task creations inherit it.
Alternative Considered
A skill-based workaround (add task creation skill that auto-populates workdir) is possible but puts the burden on the user rather than solving it natively in the kanban system.