GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — RFC-001: Multi-Agent Visual Indicator for Active Sessions by vikramrajj · Pull Request #818 · CommandCodeAI/command-code

Conversation

vikramrajj commented Sep 8, 2026

Copy link

Copy Markdown

Summary

This PR adds RFC-001 — a detailed design proposal for implementing a multi-agent visual indicator in the Command Code CLI, as requested in issue #817.

What's Included

RFC document (rfcs/001-multi-agent-visual-indicator.md) with:
- TypeScript interfaces for agent status tracking
- Component designs (AgentBadge, AgentStatusBar)
- Integration approach with existing session state
- Settings schema for user configuration
- Visual mockups for compact/detailed/minimal styles
- Phased migration path (passive → interactive → advanced)

Key Design Decisions

Three display styles: compact (default), detailed, minimal
Status lifecycle: queued → running → completed/failed/killed
Non-intrusive: Status bar sits above conversation, auto-hides when no agents active
Configurable: Via agentIndicator settings object
Phased rollout: Start with passive indicator, add interactivity later

Visual Inspiration

T3 Code (Theo) — agent badges with spinners
Codex — agent tiles with status indicators

Next Steps

If approved, implementation would proceed in three phases:

Passive indicator (read-only display)
Interactive controls (expand, kill, view output)
Advanced features (timeline, metrics, streaming)

Related issue: #817

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions


          feat(rfc): add multi-agent visual indicator design (RFC-001)

201b4a4

Draft RFC for showing active agents in session with visual indicators.
Includes TypeScript interfaces, component designs, and integration approach.

Co-authored-by: CommandCodeBot <[email protected]>

ahrazzle suggested changes

Sep 22, 2026

View reviewed changes

ahrazzle left a comment •

edited

Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting changes. This RFC declares behaviour it does not implement, renders agent-produced text with no escape rules, diverges from the cited issue, and creates a new repository convention with no recorded decision.

Scope

Reviewed head 201b4a4 with one added file, rfcs/001-multi-agent-visual-indicator.md, checked against itself and the repository governance records.

Blocking findings

Unrecorded rfcs/ convention. The PR creates a new top level rfcs/ directory and numbers this document RFC-001.
Code search finds no other rfcs/ path, and there is no contributing guide or pull request template.
No precedent for a design document PR in recent history either way.
Do the maintainers want an rfcs/ convention at all? If so, record approval in this thread.
Unread declared fields. animate at rfcs/001-multi-agent-visual-indicator.md:94 and showUsage at rfcs/001-multi-agent-visual-indicator.md:92 are declared and never read.
color at rfcs/001-multi-agent-visual-indicator.md:58 and progress at rfcs/001-multi-agent-visual-indicator.md:67 are declared and never read.
The minimal style at rfcs/001-multi-agent-visual-indicator.md:88 has no branch. Only rfcs/001-multi-agent-visual-indicator.md:194 branches, for detailed.
The compact prop at rfcs/001-multi-agent-visual-indicator.md:118 is never passed at rfcs/001-multi-agent-visual-indicator.md:197.
The typescript fence at rfcs/001-multi-agent-visual-indicator.md:110 holds JSX, failing a .ts parse and parsing only as tsx.
Undefined symbols. truncate at rfcs/001-multi-agent-visual-indicator.md:154 and generateId at rfcs/001-multi-agent-visual-indicator.md:220 are called and never defined.
renderAgentStatusBar at rfcs/001-multi-agent-visual-indicator.md:229 and rfcs/001-multi-agent-visual-indicator.md:240 is called and never defined.
AgentStartParams at rfcs/001-multi-agent-visual-indicator.md:219 and AgentResult at rfcs/001-multi-agent-visual-indicator.md:234 have no definitions.
The session store at rfcs/001-multi-agent-visual-indicator.md:213 has no import or initialization. The render trigger implies a re-render mechanism the document never shows.
Unreachable states. rfcs/001-multi-agent-visual-indicator.md:225 always sets running. rfcs/001-multi-agent-visual-indicator.md:237 produces only completed or failed.
The queued and killed states have no production path. Session end cleanup at rfcs/001-multi-agent-visual-indicator.md:295 is prose with no handler.
The click interaction at rfcs/001-multi-agent-visual-indicator.md:305 assumes terminal capabilities the document never verifies.
Missing sanitisation. Agent controlled name at rfcs/001-multi-agent-visual-indicator.md:56, description at rfcs/001-multi-agent-visual-indicator.md:154 and error text at rfcs/001-multi-agent-visual-indicator.md:238 render into terminal output with no stated escape rules.
The color field at rfcs/001-multi-agent-visual-indicator.md:57 accepts hex or ansi color with no stated validation.
A sanitisation subsection is needed before implementation.
Divergence from issue 817. Issue 817 specifies showAgentIndicator and agentIndicatorStyle with compact, detailed or none.
The document uses agentIndicator at rfcs/001-multi-agent-visual-indicator.md:249 with a different field set and minimal in place of none.
The recorded maintainer position on issue 817 describes a narrower explorer on the roadmap, while the document proposes three broader phases with no recorded approval for the wider scope.

Requested changes

Define or remove unused fields.
Define undefined symbols or mark them out of scope.
Give queued and killed production paths or remove them.
Add sanitisation rules.
Align settings keys with issue 817 or record divergence with maintainer approval.
Record the rfcs/ convention decision.

Limits

The repository has no source for the product internals this document specifies, and with no test suite or CI those internals were not validated here.

Automated posting by agentic team with human oversight.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md

		@@ -0,0 +1,336 @@
		# RFC-001: Multi-Agent Visual Indicator for Active Sessions

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Creating a new top level rfcs/ directory and numbering this document RFC-001 is a convention decision. The repository has no contributing guide, no pull request template and no other rfcs path, so the maintainers may want to weigh in before this becomes the pattern for later documents.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md

		/** Show token usage on completion */
		showUsage: boolean;
		/** Animation enabled for running state */
		animate: boolean;

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This option is declared here, defaulted at line 104, and listed in the settings block at line 254, but no component in the document reads it. The same holds for showUsage (line 92), color (line 58) and progress (line 67). Implementing or removing them would keep the specification honest.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md


		### Status Badge Component

		```typescript

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This fence is labelled typescript but contains JSX, which does not parse as .ts (TS1005 errors start at line 33 of the block). It parses as .tsx, leaving only the unresolved module and cross-block names. Labelling the fence tsx would save an implementer the detour.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md

		<Box borderStyle="round" borderColor={color} paddingX={1} marginRight={1}>
		<Text color={color}>{icon} </Text>
		<Text bold>{agent.name}</Text>
		<Text dimColor> — {truncate(agent.description, 40)}</Text>

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agent.description here and agent.error at line 238 are agent-produced text rendered into the terminal. Truncating to 40 characters does not strip ANSI escape sequences or newlines, and the document states no sanitisation rule anywhere. Worth specifying before implementation.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md

		</Box>

		{/* Detailed badges (if style is 'detailed') */}
		{config.style === 'detailed' && (

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only style branch in the component. The minimal style declared at line 88 therefore renders identically to compact, and the dots-only rendering shown in the mockup at line 285 is not produced by any code in the document.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md

		id: agentId,
		name: params.agentName,
		description: params.taskDescription,
		status: 'running',

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

handleAgentStart always writes running, and handleAgentComplete at line 237 writes only completed or failed. The queued and killed members of AgentStatus (line 50) have no production path, although the summary line counts queued at line 190 and the mockups show both.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md

		startedAt: Date.now(),
		};
		sessionState.activeAgents.set(agentId, activeAgent);
		renderAgentStatusBar(); // Trigger re-render

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

renderAgentStatusBar is not defined anywhere in the document, and neither are truncate (line 154), generateId (line 220), AgentStartParams (line 219) or AgentResult (line 234). Mutating an entry of a Map does not by itself re-render an Ink tree, so the render trigger needs a defined mechanism.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Comment thread

rfcs/001-multi-agent-visual-indicator.md


		```json
		{
		"agentIndicator": {

ahrazzle Sep 22, 2026

Copy link

Copy Markdown

Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue #817 proposes showAgentIndicator and agentIndicatorStyle with the values compact, detailed or none. This block uses a different key and field set and uses minimal where the issue uses none. Aligning the two or recording the divergence would help whoever implements it.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

Reviewers

1 more reviewer

ahrazzle

ahrazzle requested changes

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.

Conversation

vikramrajj commented Sep 8, 2026

Summary

What's Included

Key Design Decisions

Visual Inspiration

Next Steps

Uh oh!

ahrazzle left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Scope

Blocking findings

Requested changes

Limits

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

ahrazzle left a comment •

edited

Loading

Uh oh!

There was an error while loading. Please reload this page.