Skip to content
Signals & Extensions

Signals & Extensions

This page answers “where is Claude Code heading.” 10 capability signals identified from path structures — not a marketing feature list but real system edges read directly from code. Classified into four maturity levels to avoid misreading prototypes as shipping features.

Visual companion: Signals page

Maturity Assessment Criteria

LevelDefinitionAssessment Basis
IntegratedMerged into the trunkHas dedicated service/tool directory, command entry, and dependencies on other subsystems
EmergingTaking shapeHas independent directory and service files, but command/UI not fully wired
PartialPartially completeHas directory and components, but appears as locally mounted capability from entry and dependency analysis
SurfaceSurface-level signalOnly command entries or single files, not an independent subsystem

Signal Overview

Signals mature enough for independent topic pages have dedicated pages; the rest remain here as an observation index.

Integrated (6 signals)

SignalConfidenceDescriptionDeep Dive
Bridge & MailboxHighCross-interface connection with bridge/ directory + mailbox context + multi-surface commandsMCP & Bridge
AutoDream & Memory HygieneHighBackground memory consolidation forming a closed loop with memdir and session memoryMemory System
Cron & Remote TriggersHighScheduleCronTool and RemoteTriggerTool provide scheduled and remote automationTool Plane
Verification Agent LaneHighAgentTool’s built-in/ includes verification, planning, and explore agentsCoordinator
Computer UseHigh15-file desktop automation subsystemComputer Use
PluginsHigh~1,700-line Schema installable extension systemPlugin System

Emerging (3 signals)

SignalConfidenceDescriptionDeep Dive
Team Memory SyncHighteamMemorySync service + teamMemPaths tool for cross-member memory sharingMemory System
Voice SurfaceMediumNative audio + STT stream + OAuth gate, Push-to-talk voice inputVoice
Coordinator ModeHigh369-line multi-Worker orchestration system with four-phase workflowCoordinator

Partial (1 signal)

Buddy Companion

Confidence: Medium

The buddy/ directory already has complete components (prompt, sprite, component — deterministic gacha, ASCII animation engine, AI observer), but from command entries it still appears as a locally mounted capability rather than a trunk feature.

Path evidence: src/buddy/

Surface (3 signals)

Context Viz & Thinkback

Confidence: Medium

ctx_viz, thinkback, and thinkback-play expose research and retrospection surface entries — letting users visualize context distribution and replay thinking processes.

Path evidence: src/commands/ctx_viz, src/commands/thinkback, src/commands/thinkback-play

UltraPlan Overlay

Confidence: Medium

The ultraplan command appears alongside plan mode tools, potentially allowing planning sessions of up to 30 minutes on Opus-class models.

Path evidence: src/commands/ultraplan, src/tools/EnterPlanModeTool/, src/tools/ExitPlanModeTool/

Statusline Setup

Confidence: Medium

The statusline command and built-in statuslineSetup agent suggest the terminal status bar is treated as an independent product surface.

Path evidence: src/commands/statusline, src/tools/AgentTool/built-in/statuslineSetup.ts

Signal Relationship Diagram

    graph LR
    subgraph Integrated
        B[Bridge & Mailbox]
        AD[AutoDream]
        CR[Cron & Triggers]
        VA[Verification Agent]
        CU[Computer Use]
        PL[Plugins]
    end
    subgraph Emerging
        TMS[Team Memory Sync]
        VS[Voice Surface]
        CO[Coordinator Mode]
    end
    subgraph Partial
        BU[Buddy Companion]
    end
    subgraph Surface
        CV[Context Viz]
        UP[UltraPlan]
        SL[Statusline Setup]
    end

    B --> AD
    AD --> TMS
    CR --> VA
    CU -.-> VS
    PL -.-> CR
    CO --> VA
    CO --> CR
    VS -.-> B
    BU -.-> VS
  

How to Use These Signals

  1. Integrated signals have independent topic pages — click the Deep Dive links above for in-depth study
  2. Emerging signals are worth watching — the next version may bring significant changes
  3. Partial and Surface signals should not be over-interpreted — they may be deprecated or suddenly mature

Reading Order

  1. Computer Use — Desktop automation subsystem
  2. Plugin System — Complete extension engineering
  3. Coordinator — Multi-Worker orchestration
  4. Voice — Voice input channel
  5. MCP & Bridge — Two core channels of the extension fabric