#Kanban - unassigned task go to ready.

1 messages · Page 1 of 1 (latest)

tired mango
split pumice
tired mango
#

I told LLM to spawn 5 kanban workers with unassigned assignees, so in theory they belong to TO DO field in kanban dashboard

#

hermes debug share: log content redacted at upload time. run with --no-redact to disable]
--- hermes dump ---
version: 0.13.0 (2026.5.7) [db84a78e]
os: Linux 6.17.0-1011-oracle aarch64
python: 3.11.15
openai_sdk: 2.24.0
profile: default
hermes_home: ~/.hermes
model: deepseek/deepseek-v4-flash
provider: nous
terminal: local

api_keys:
openrouter set
openai not set
anthropic not set
anthropic_token not set
nous not set
google/gemini not set
gemini not set
glm/zai not set
zai not set
kimi not set
minimax not set
deepseek not set
dashscope not set
huggingface not set
nvidia not set
ai_gateway not set
opencode_zen not set
opencode_go set
kilocode not set
firecrawl set
tavily set
browserbase not set
fal not set
elevenlabs not set
github set

features:
toolsets: hermes-cli, web
mcp_servers: 0
memory_provider: mnemosyne
gateway: running (systemd (user), pid 863219)
platforms: telegram
cron_jobs: 1 active / 1 total
skills: 116

config_overrides:
agent.max_turns: 100
agent.tool_use_enforcement: True
terminal.persistent_shell: False
compression.threshold: 0.8
display.streaming: True
display.show_reasoning: True
toolsets: ['hermes-cli', 'web']
fallback_providers: [{'model': 'deepseek-v4-flash', 'provider': 'opencode-go'}]
--- end dump ---

split pumice
#

can i get the logs please?

#

hermes debug share check through to see there's nothing you don't mind sharing, then send the links over.

tired mango
split pumice
#

links instead of screenshots please

#

the command outputs links. please share those here with me.

tired mango
#

Sure, prepping

split pumice
#

Thanks. Please also include the exact prompt you gave Hermes to spawn the 5 workers.

tired mango
#

no matter what I do its easily reproducible with simplest ways, eg i add task in dashboard to TO DO field naming it whatever and hit create... it goes immediately to ready field despite having unassigned profile

#

if I do it simply in CLI with just kaban create no matter how complicated or simple its the same result

#

hermes kanban create "Stage 3B: implement corrections — nights-dark-masters-2ed.txt"
--workspace dir:/home/ubuntu/projects/datasets/wfrp-CPT
--tenant wfrp-cpt-cleaning
--skill file-system-navigation --skill ocr-integrity-report --skill kanban-worker
--skill systematic-debugging --skill robust-pipeline-validator \

#

clean hermes agent with mnemosyne and web search plus from non official, runnin on VPS arm cpu instance without docker, Local backend. Installed with one liner as far as i remember and perhaps --user

#

ah. maybe important but I run dashboard with --insecure /tailscale/

#

but without --tui its same

split pumice
#

Thanks, that repro helps.

This looks like current Kanban behavior plus confusing dashboard wording.

In the backend, a newly-created task with no parents and no --triage flag starts as ready even if it has no assignee. The dispatcher then skips ready tasks that have no assignee, so they should not actually spawn until you assign a profile.

So in current Hermes, ready means "dependencies are satisfied / this can run once it has a runnable assignee." It does not strictly mean "already assigned." That makes the dashboard subtitle misleading here, because it says Ready is "assigned and waiting for dispatcher tick" while the backend allows unassigned ready tasks.

Your command is enough to hit that path because it creates parent-free tasks without --assignee:

hermes kanban create "..." --workspace ... --tenant ... --skill ...

If you want those tasks to run, create or move them with a real assignee/profile. If you want raw unspecced ideas parked before they become runnable work, use --triage.

There is not currently a stable "parent-free but forced TODO forever" state, because the ready recompute path promotes TODO tasks to READY once their dependencies are satisfied, and a task with no parents already satisfies that condition.

I’ll track the dashboard wording/UX mismatch separately, because the UI currently makes the READY column sound stricter than the backend state actually is.

#

@summer needle small Kanban dashboard UX mismatch when you have a sec:

Backend semantics currently allow unassigned parent-free tasks to land in ready. The dispatcher then skips them as skipped_unassigned, so they do not actually spawn until assigned.

The dashboard Ready column currently says ASSIGNED AND WAITING FOR DISPATCHER TICK, which made a user think unassigned cards in Ready were invalid. Could we update the copy/tooltips so Ready means dependency-ready, not necessarily assigned?

Possible copy:
Ready: DEPENDENCIES SATISFIED; ASSIGN A PROFILE TO DISPATCH

And for unassigned cards in Ready, maybe show a small hint/badge like:
Needs assignee

I would not move them client-side into TODO, because that would disagree with the persisted backend status. This is mostly a frontend wording/affordance issue unless we decide to change Kanban semantics separately.

summer needle
#

Looking

summer needle
summer needle
#

merged