1jehuang / 1jehuang/jcode

Show worker model name in the live swarm strip for ongoing agents

Open
#1,005 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

autonomous: no enhancement triage: needs-decision ux
Dominant language
Rust
Stars
19.9k
Forks
2.3k
Avg merge
2d 7h
Merged PRs (30d)
30

Description

Jcode's completed swarm agent cards already show the worker model, for example:

<icon> <title> · Completed · GPT-5.4 · <auth route>

But the always-visible live swarm strip for ongoing agents only shows the icon/name and task, so while agents are still running it is hard to tell which worker is using which model.

Expected behavior:

🐝 ⠙ 🦊 · GPT-5.5 · investigate renderer

This would help coordinators who run multiple workers with different models at the same time, such as one GPT worker for implementation and one Claude worker for review.

Implementation note: the strip renderer already receives model data. GalleryMember.model is populated from member.runtime.model in crates/jcode-tui/src/tui/info_widget_swarm_gallery.rs:88, and completed cards already render it. The compact strip path in crates/jcode-tui-render/src/swarm_gallery.rs builds a local Chip for ongoing rows around line 600 with glyph, name, task, todo, color, and is_sel, but no model. Adding a model field there and rendering it when width allows should be enough for the horizontal strip; the vertical compact row in the same file can use member.model directly with the existing width-budget logic.

If showing the model name by default feels too noisy, please make it configurable instead. Based on the existing [agents] config style (swarm_strip_layout, swarm_spawn_mode, swarm_model), a name like agents.swarm_strip_show_model = true|false would fit better than adding an unrelated display option.


Drafted by gpt-5.5.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in crates/jcode-tui-render/src/swarm_gallery.rs around the compact horizontal strip near line 600, then compare its local Chip with the model rendering used for completed cards. Trace GalleryMember.model from crates/jcode-tui/src/tui/info_widget_swarm_gallery.rs:88 and make the ongoing horizontal and vertical rows show the worker model within their width budgets, or confirm the requested configuration behavior if default display is considered too noisy.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.