BitSquare/Codeman
2
0
Fork 0
mirror of https://github.com/Ark0N/Codeman.git synced 2026-10-06 07:29:42 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix: read subagent descriptions directly from parent transcript

Browse Source 
Instead of timing-based correlation between terminal output and subagent
files, now reads the Task tool's description parameter directly from the
parent session's transcript. This provides 100% reliable mapping between
agent IDs and their short descriptions, fixing issues where multiple
agents spawned in quick succession would get the same window title.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
arkon
2026-01-26 11:06:35 +01:00
co-authored by Claude Opus 4.5
parent 1c9a7dc077
commit 32e0d6126c
4 changed files with 120 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/web/server.ts
+4 -39
View File
@@ -318,16 +318,13 @@ export class WebServer extends EventEmitter {
/**
* Set up event listeners for subagent watcher.
* Broadcasts real-time subagent activity to SSE clients.
*
* The SubagentWatcher now extracts descriptions directly from the parent session's
* transcript, which contains the exact Task tool call with the description parameter.
* This is more reliable than the previous timing-based correlation approach.
*/
private setupSubagentWatcherListeners(): void {
subagentWatcher.on('subagent:discovered', (info: SubagentInfo) => {
// Try to get a better description from the session's TaskTracker
// The TaskTracker has access to params.description from the Task tool call
const betterDescription = this.getTaskDescriptionForSubagent(info);
if (betterDescription && betterDescription !== info.description) {
info.description = betterDescription;
subagentWatcher.updateDescription(info.agentId, betterDescription);
}
this.broadcast('subagent:discovered', info);
});
@@ -360,38 +357,6 @@ export class WebServer extends EventEmitter {
});
}
/**
* Get the short description from TaskTracker for a discovered subagent.
*
* When Claude Code spawns a subagent via the Task tool, it passes two parameters:
* - description: Short title like "Explore Python scripts" (3-5 words)
* - prompt: Full detailed task prompt
*
* The TaskTracker parses the Task tool call and has access to params.description,
* while the SubagentWatcher only sees the JSONL file which contains the full prompt.
*
* This method correlates them by finding the session whose working directory
* matches the subagent's project hash, then checking for recent tasks.
*/
private getTaskDescriptionForSubagent(info: SubagentInfo): string | undefined {
// Find sessions whose working directory matches this subagent's project
// Check ALL matching sessions since multiple sessions may have the same working directory
const subagentStartTime = new Date(info.startedAt).getTime();
for (const session of this.sessions.values()) {
const sessionProjectHash = subagentWatcher.getProjectHashForDir(session.workingDir);
if (sessionProjectHash === info.projectHash) {
// Found a matching session - check for recent task descriptions parsed from terminal
// The Session parses "Explore(Description)" patterns from Claude Code output
const description = session.findTaskDescriptionNear(subagentStartTime, 15000);
if (description) {
return description;
}
}
}
return undefined;
}
private async setupRoutes(): Promise<void> {
// Serve static files
await this.app.register(fastifyStatic, {