Skip to content

Other CLI adaptability? #81

@rackerism

Description

@rackerism

1. The Goal

Transition Pixel Agents from a Claude Code extension into an Open Agent Workspace. By supporting multiple CLI-based agents, the extension becomes the central "Command Center" for a user's entire AI workforce, regardless of which model or company powers the terminal.

2. Implementation Strategy: The "Agent Profile" Model

Rather than hardcoding logic for each CLI, implement a Profile System where each agent type is defined by a simple JSON configuration.

Feature | Current (Claude Only) | Recommended (Adaptive) -- | -- | -- Trigger | Watches .claude.jsonl | Watches a configurable file path or stdout stream. Parsing | Specific to Claude tool schemas. | Uses a "Regex Mapper" to link tool calls to animations. Character | Assigned at spawn. | Linked to the specific CLI profile (e.g., Gemini = "Robot", Claude = "Scholar").

3. Key CLIs to Integrate

  • Gemini CLI: Since it now supports Extensions and MCP, a "Gemini Agent" in the office could visually represent when it’s querying Google Cloud or searching the web.

  • Cline CLI 2.0: This is highly agentic and runs parallel instances. Visualizing Cline agents alongside Claude agents would solve the "multi-window management" headache users currently face.

  • GitHub Copilot CLI: Perfect for visualizing "Headless" background tasks like automated PR reviews.

4. Technical Recommendation: "Universal Transcript"

Suggest creating a lightweight shim or wrapper that other CLIs can pipe into.

  • Example: gemini-cli "refactor this" | pixel-agents-bridge

  • This bridge would convert any CLI output into the JSONL format Pixel Agents already understands, making the extension instantly compatible with any tool that prints to the terminal.


Why this adds value:

  • Reduced Context Switching: Users can see the status of a Gemini task and a Claude task in one visual office.

  • Vendor Agility: As new agents (like Codex or OpenCode) gain popularity, Pixel Agents remains relevant because it isn't tied to a single API.

  • Market Position: It moves the project from a "plugin" to a "platform" for terminal-based AI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: providersMulti-provider support: Codex, Copilot, OpenCode, Kiro, etc.type: discussionQuestion, idea, or open-ended conversation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions