hermes - 💡(How to fix) Fix [Feature]: Workspace kind and patch input in Kanban - Dashboard [1 participants]

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…
GitHub stats
NousResearch/hermes-agent#18718Fetched 2026-05-03 04:54:44
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Root Cause

Hello! I would like the have two inputs to change: "workspace_kind" and "workspace_path". This is very important because it completely makes useless the dashboard where kanban should be much better because of the UI, but without this, I can't work with worktrees or directly asking to work in some directory...

RAW_BUFFERClick to expand / collapse

Problem or Use Case

Hello! I would like the have two inputs to change: "workspace_kind" and "workspace_path". This is very important because it completely makes useless the dashboard where kanban should be much better because of the UI, but without this, I can't work with worktrees or directly asking to work in some directory...

Proposed Solution

Add both inputs or extend the api (or documentation to allow us to do that extending the dashboard with plugins)

Alternatives Considered

No response

Feature Type

Configuration option

Scope

Small (single file, < 50 lines)

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

extent analysis

TL;DR

Add "workspace_kind" and "workspace_path" inputs to the existing configuration options to enhance the dashboard functionality.

Guidance

  • Review the current configuration options to determine the best way to integrate the new inputs, considering the existing code structure and potential impact on other features.
  • Consider extending the API or documentation to allow for plugin-based extensions, as proposed in the issue, to provide a more flexible solution.
  • Evaluate the scope of the change, focusing on a single file with less than 50 lines of code, to minimize the complexity and potential risks of the update.
  • Assess the potential benefits of allowing users to work with worktrees or specific directories, and how the new inputs will address these needs.

Notes

The issue lacks specific technical details about the current implementation, so it's essential to carefully review the existing code and configuration options before making any changes.

Recommendation

Apply workaround: Add the proposed inputs to the configuration options, as this seems to be a targeted and relatively small change that can address the user's needs.

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…

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]: Workspace kind and patch input in Kanban - Dashboard [1 participants]