Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Feature]: hermes kanban edit should support --skills, --reset-failures, and --clear-claim for common recovery without direct DB access

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The hermes kanban edit command currently only supports --result and --summary. For the most common recovery operations — clearing invalid skills, resetting consecutive_failures, and clearing stale claim locks — operators must resort to direct SQLite manipulation:

DB=~/.hermes/kanban/boards/<board-slug>/kanban.db

# Clear bogus skills that cause "Unknown skill(s)" crashes
sqlite3 "$DB" "UPDATE tasks SET skills = "[]" WHERE id = "t_xxx";"

# Reset failure counter and claim to make task eligible for dispatch again
sqlite3 "$DB" "UPDATE tasks SET consecutive_failures = 0, status = "ready",
  claim_lock = NULL, claim_expires = NULL, worker_pid = NULL,
  last_failure_error = NULL, current_run_id = NULL
  WHERE id = "t_xxx";"

This is fragile (schema could change), error-prone (easy to typo a column name), and not documented in the CLI help.

Error Message

This is fragile (schema could change), error-prone (easy to typo a column name), and not documented in the CLI help.

Root Cause

The hermes kanban edit command currently only supports --result and --summary. For the most common recovery operations — clearing invalid skills, resetting consecutive_failures, and clearing stale claim locks — operators must resort to direct SQLite manipulation:

DB=~/.hermes/kanban/boards/<board-slug>/kanban.db

# Clear bogus skills that cause "Unknown skill(s)" crashes
sqlite3 "$DB" "UPDATE tasks SET skills = "[]" WHERE id = "t_xxx";"

# Reset failure counter and claim to make task eligible for dispatch again
sqlite3 "$DB" "UPDATE tasks SET consecutive_failures = 0, status = "ready",
  claim_lock = NULL, claim_expires = NULL, worker_pid = NULL,
  last_failure_error = NULL, current_run_id = NULL
  WHERE id = "t_xxx";"

This is fragile (schema could change), error-prone (easy to typo a column name), and not documented in the CLI help.

Fix Action

Fix / Workaround

Reset failure counter and claim to make task eligible for dispatch again

sqlite3 "$DB" "UPDATE tasks SET consecutive_failures = 0, status = "ready", claim_lock = NULL, claim_expires = NULL, worker_pid = NULL, last_failure_error = NULL, current_run_id = NULL WHERE id = "t_xxx";"


# Reset failure counter and claim lock (full reset to re-dispatchable)
hermes kanban edit t_xxx --reset-failures
hermes kanban edit t_xxx --clear-claim

Code Example

DB=~/.hermes/kanban/boards/<board-slug>/kanban.db

# Clear bogus skills that cause "Unknown skill(s)" crashes
sqlite3 "$DB" "UPDATE tasks SET skills = "[]" WHERE id = "t_xxx";"

# Reset failure counter and claim to make task eligible for dispatch again
sqlite3 "$DB" "UPDATE tasks SET consecutive_failures = 0, status = "ready",
  claim_lock = NULL, claim_expires = NULL, worker_pid = NULL,
  last_failure_error = NULL, current_run_id = NULL
  WHERE id = "t_xxx";"

---

# Clear invalid skills
hermes kanban edit t_xxx --skills []
hermes kanban edit t_xxx --clear-skills

# Reset failure counter and claim lock (full reset to re-dispatchable)
hermes kanban edit t_xxx --reset-failures
hermes kanban edit t_xxx --clear-claim

# Combined convenience
hermes kanban reset t_xxx  # equivalent to --reset-failures + --clear-claim + status=ready
RAW_BUFFERClick to expand / collapse

Summary

The hermes kanban edit command currently only supports --result and --summary. For the most common recovery operations — clearing invalid skills, resetting consecutive_failures, and clearing stale claim locks — operators must resort to direct SQLite manipulation:

DB=~/.hermes/kanban/boards/<board-slug>/kanban.db

# Clear bogus skills that cause "Unknown skill(s)" crashes
sqlite3 "$DB" "UPDATE tasks SET skills = "[]" WHERE id = "t_xxx";"

# Reset failure counter and claim to make task eligible for dispatch again
sqlite3 "$DB" "UPDATE tasks SET consecutive_failures = 0, status = "ready",
  claim_lock = NULL, claim_expires = NULL, worker_pid = NULL,
  last_failure_error = NULL, current_run_id = NULL
  WHERE id = "t_xxx";"

This is fragile (schema could change), error-prone (easy to typo a column name), and not documented in the CLI help.

Proposed CLI Extensions

# Clear invalid skills
hermes kanban edit t_xxx --skills []
hermes kanban edit t_xxx --clear-skills

# Reset failure counter and claim lock (full reset to re-dispatchable)
hermes kanban edit t_xxx --reset-failures
hermes kanban edit t_xxx --clear-claim

# Combined convenience
hermes kanban reset t_xxx  # equivalent to --reset-failures + --clear-claim + status=ready

Suggested Fix

Extend hermes kanban edit with flags for the most common recovery operations, backed by the same SQL but with validation and schema-awareness. Add a hermes kanban reset convenience command for the full recovery path.

Environment

  • Hermes Agent v2.x
  • The kanban-orchestrator skill references document (references/kanban-db-recovery.md) contains the full schema and recovery SQL

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Feature]: hermes kanban edit should support --skills, --reset-failures, and --clear-claim for common recovery without direct DB access