Add template/workspace icons to tasks list for better workspace identification
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by locating the tasks-list UI and the data used for each task's workspace or template; the issue provides no file or test names. Use the listed workspace examples as cases, then verify the tasks list shows a workspace or template icon beside each task and remains distinguishable across workspaces.
Written by the indexing model from the issue text.
Description
Summary
Add visual indicators (template/workspace icons) to the tasks list to help users quickly identify which workspace each task belongs to.
Current Behavior
The tasks list shows task names with workspace identifiers in the text (e.g., task-coder-issue-17417-f532, task-mcp-tools-inventory-b813), but there's no visual differentiation between tasks from different workspaces.
Proposed Enhancement
Add small template or workspace icons next to each task in the list to provide visual cues that help users quickly distinguish between tasks from different workspaces (e.g., coder, mcp-tools, albridge).
Screenshot
Benefits
- Improved visual scanning and task identification
- Easier to distinguish between tasks from different workspaces at a glance
- Better UX for users managing multiple workspaces simultaneously
- Dominant language
- TypeScript
- Stars
- 165
- Forks
- 20
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/blink
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
GitHub tools `list_user_installations` and `list_app_installations` fail with app installation authOpen
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#33286 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
friction
Difficulty 1/5 Under an hour Newbie friendliness 77/100
kentcdodds/kody#4499 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hemilabs/ui-monorepo#2605 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 6 days
-
build.yml: macOS arm64 DMG fails, cargo missing on the macos-26 runner imagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getopenscreen/openscreen#1423 ·
Maintainers usually reply within 1 day