Skip agents with parentAgentId when building the aggregated agents list
for the homepage. This ensures only top-level (root) agents are displayed,
while child agents are only accessible through their parent agent's menu.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add parentAgentId optional parameter to the create_agent MCP tool input
schema so agents can create child agents with explicit parent references.
Also update registerSession() to copy parentAgentId from config to the
managed agent object.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add parentAgentId field to enable agent parent/child hierarchy:
- ManagedAgentBase in agent-manager.ts
- AgentSessionConfig in agent-sdk-types.ts
- AgentSnapshotPayloadSchema in messages.ts
- toAgentPayload() in agent-projections.ts
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Design complete for agent parent/child hierarchy feature:
- parentAgentId field to track agent relationships
- MCP create_agent tool auto-sets parent from calling agent
- Homepage filters to show only root agents
- Agent menu shows sub-agents with navigation
Added implementation tasks:
- Server types (agent-manager, agent-sdk-types, agent-projections)
- MCP server integration
- Client types (session-store, agent-directory, messages)
- Homepage filtering
- Agent menu sub-agents section
- End-to-end test task
- Re-audit plan task
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Tested via Playwright MCP:
- Navigated to agent screen, clicked "View Changes"
- Git diff loaded successfully showing changes to plan.md
- Only one git_diff_request sent (no infinite loop)
- setGitDiffs called once and content rendered correctly
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Added hasRequestedRef to track if a git diff request was already made
for the current agentId. This prevents duplicate requests when the
requestGitDiff function reference changes due to store updates.
The issue was that requestGitDiff in the useEffect dependency array
caused an infinite loop: request → store update → new function ref →
effect re-runs → request again.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Tested that Claude agent uses Opus 4.5 after SDK update to 0.1.75.
Agent correctly reports running on claude-opus-4-5-20251101 and
the model is properly displayed in the agent info menu.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Updated @anthropic-ai/claude-agent-sdk from 0.1.74 to 0.1.75.
This version includes Opus 4.5 model (claude-opus-4-5-20251101).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Root cause identified: Infinite loop in git-diff.tsx due to unstable
requestGitDiff function reference. The useEffect depends on this
function which changes on every store update, causing repeated
git_diff_request calls (250+ times in seconds).
Added findings section documenting:
- Data flow analysis showing the dependency chain
- The exact loop mechanism
- Console evidence (setGitDiffs/setSessionMethods called 250+ times)
- Required fix: remove requestGitDiff from useEffect dependencies
Added follow-up tasks:
- Fix task to remove unstable dependency
- Test task to verify git diff loads correctly
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Re-audit confirms all model info tracking tasks are complete:
- Claude SDK investigation found model in init message
- Implementation captures model in handleSystemMessage()
- Fixed refreshRuntimeInfo() to emit state on changes
- Both Claude and Codex agents show actual runtime models
- All tests passed
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Created Claude agent with "Automatic" model config. Agent correctly
self-reported running on claude-opus-4-1-20250805 (Opus 4.1), and
the agent info menu now displays the correct runtime model instead
of "Unknown". The fix for capturing model from SDK init message and
emitting state after runtimeInfo changes is working correctly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Created a new Claude agent with "Automatic" model config.
The agent responded correctly stating it runs on Claude Opus 4.1.
However, the model still shows "Unknown" in the agent info menu.
Root cause: The server wasn't restarted after the fix was implemented.
The dev server uses tsx with explicit restart messaging - it doesn't
auto-reload on file changes. The fix code exists in source but the
server is running stale code.
Added follow-up tasks:
- Restart server to apply model capture fix
- Re-test Claude model display after server restart
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The Claude agent model was not showing in the UI ("Model: Unknown") because
refreshRuntimeInfo() updated agent.runtimeInfo but never called emitState()
to notify connected clients of the change.
Fixed by:
1. Adding change detection in refreshRuntimeInfo() to check if model, sessionId,
or modeId changed
2. Calling emitState(agent) when changes are detected
3. Added debug logging in handleSystemMessage() to confirm model capture
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Created Claude agent with 'Automatic' model config. Agent self-reported
running on claude-opus-4-1-20250805 (Opus 4.1), but UI shows 'Model: Unknown'
in agent info menu.
The implementation to capture model from SDK init message is not working -
model is not being propagated to the UI.
Added fix task and re-test task to address the issue.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Tested Codex agent creation with "Automatic" model config.
After first turn completion, UI correctly displays `gpt-5.1-codex-max`
(actual runtime model from rollout file), confirming runtime model
detection is working correctly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Update handleSystemMessage() in claude-agent.ts to read the actual model
from the SDK's init message (message.model) instead of just echoing back
the configured model. This gives us the real runtime model that the SDK
selected.
Also invalidates cached runtime info when the model is updated to ensure
getRuntimeInfo() returns the new value.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Investigated @anthropic-ai/claude-agent-sdk types and found that actual
model info is exposed in two places:
1. SDKSystemMessage (init) has `model` field
2. SDKResultMessage has `modelUsage` with model names as keys
Current implementation ignores both, only using config.model.
Added implementation task to capture actual model from init message.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Completed audit of current model info tracking implementation:
- Model config set via AgentSessionConfig.model
- Runtime info uses AgentRuntimeInfo type with model field
- UI correctly uses extractAgentModel() which reads runtimeInfo.model
Key findings:
- Codex agents: Correctly detect runtime model from rollout file ✓
- Claude agents: Currently echo configured model (not runtime detected)
- Gap: Claude SDK may expose actual model in response metadata
Added follow-up tasks:
- Investigate if Claude SDK exposes actual model in responses
- Test Codex runtime model detection
- Test Claude agent model display behavior
- Re-audit plan after investigation
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Problem: After migrating to pure Zustand, useDaemonSession returned only
SessionState from the store, but components need both state AND imperative
APIs (like sendAgentMessage, createAgent, etc.).
Solution: Create DaemonSession type that combines:
- SessionState (from Zustand store)
- Imperative APIs (from SessionContext)
- Wrapped store actions (getDraftInput, setFocusedAgentId, etc.)
Changes:
- Added DaemonSession type to use-daemon-session.ts
- useDaemonSession now merges sessionState + context + store actions
- Wraps store actions to bind serverId automatically
- Updated prop types in components to use DaemonSession
- Fixed use-session-directory.ts to use SessionState
This restores component compatibility while keeping pure Zustand architecture.
Still TODO: Fix remaining components that use SessionContext directly
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Replace subscription-based session accessor pattern with direct snapshot updates in daemon connections context. Add sessionReady flag to connection state to track when initial agent list has been received. Auto-select first ready host in create agent modal. Migrate from app.json to app.config.js. Add android:release script and Playwright testing docs.
The agent list on the home screen now displays all agents in a single flat
list rather than grouped by host. Each row shows a host badge next to the
agent title so users can still identify which host an agent belongs to.
Agents are sorted globally by status (running first) then by most recent
activity, providing a unified view across all hosts.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
The availability check was failing for online hosts due to a timing
issue: connectionStates would show "online" before SessionProvider
registered its session accessor, causing session to be null.
Changed selectedDaemonIsUnavailable to selectedDaemonIsOffline which
only checks connectionStates status (the single source of truth for
connection state), removing the redundant session and ws.isConnected
checks. isTargetDaemonReady still requires session for actual operations.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
useAggregatedAgents now returns { groups, isLoading } where isLoading is true
while the daemon registry loads or while hosts are connecting without a session.
HomeScreen shows an ActivityIndicator during loading, then either the agent
list or empty state. Offline hosts don't block loading—only connecting hosts do.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Host health now only displays in Settings. The home screen no longer
shows offline/connecting/error banners for hosts, following the
principle that a stopped host is not an error.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Change placeholder text from "My Server" to "My Host"
- Change restart success alert title from "Server reachable" to "Host reachable"
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Introduce DaemonRegistry and DaemonConnections contexts for managing multiple server connections. Add session directory for aggregating agents across daemons, with automatic routing based on agent/server context.
Key changes:
- Add daemon profile management (add/edit/remove/set default)
- Implement connection state tracking with reconnection and exponential backoff
- Create useAggregatedAgents hook for unified agent list across daemons
- Add useDaemonSession and useDaemonRequest hooks for daemon-scoped operations
- Update agent routes to include serverId for proper session routing
- Add connection health indicators on home screen and settings
- Persist session snapshots per daemon for faster hydration on reconnect
- Guard screens gracefully when target daemon is offline
- Add React Query for consistent loading/error state management
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
