@kendoo.agentdesk/agentdesk 0.8.0 → 0.8.2

package/README.md

@@ -79,6 +79,7 @@ agentdesk update                       Update to the latest version
 |------|-------------|
 | `--description`, `-d` | Task description or requirements |
 | `--cwd` | Working directory (defaults to current) |
+| `--legacy` | Use single-process mode (cheaper, less independent reasoning) |
 
 ## Configuration
 
@@ -115,12 +116,22 @@ AgentDesk also auto-discovers agents from `.claude/agents/`, `.claude/commands/`
 
 ## How It Works
 
+Each agent runs as its own independent Claude session — not one model role-playing multiple personas. This produces genuine independent reasoning, real disagreements, and better output.
+
 1. You run `agentdesk team TASK-ID` in your project directory
 2. AgentDesk detects your project type, reads `CLAUDE.md`, and discovers existing agents
-3. The team collaborates in structured phases: **Intake** > **Brainstorm** > **Planning** > **Execution** > **Review**
-4. The session streams live to [agentdesk.live](https://agentdesk.live) where you can watch and send messages to the team
-5. For UI tasks, the team captures screenshots (desktop + mobile) and uploads them to your task tracker
-6. Token usage is tracked and displayed per session
+3. The orchestrator manages 5 phases: **Intake** > **Brainstorm** > **Planning** > **Execution** > **Review**
+4. In brainstorm/planning/review, all agents run **in parallel** — each gets their own Claude session
+5. In execution, agents run sequentially: Dennis implements > Sam audits > Luna+Mark review > Vera tests > Bart QA
+6. The session streams live to [agentdesk.live](https://agentdesk.live) where you can watch and send messages to the team
+7. Token usage is tracked and displayed per session
+
+### Session Modes
+
+| Mode | Command | Description |
+|------|---------|-------------|
+| Sub-agents (default) | `agentdesk team -d "..."` | Each agent is an independent Claude session. Better reasoning, ~4-5x tokens. |
+| Legacy | `agentdesk team -d "..." --legacy` | Single Claude process, all agents as personas. Cheaper, less independent. |
 
 ## Daemon (Remote Sessions)
 

package/cli/agent-prompts.mjs

@@ -10,7 +10,12 @@ const PHASE_INSTRUCTIONS = {
 3. Check for existing PRs: \`gh pr list --search <task-id> --json number,title,state\`
 4. Explore the codebase briefly to understand what we're working with.
 5. Summarize: what needs to be done, what already exists, and what the starting point is.
-6. Recommend which phase to start from (BRAINSTORM for new work, EXECUTION if branch exists).`,
+6. Recommend which phase to start from (BRAINSTORM for new work, EXECUTION if branch exists).
+
+IMPORTANT: At the end of your intake summary, you MUST provide a short title for this session on its own line in this exact format:
+SESSION_TITLE: <4-8 word title>
+Example: SESSION_TITLE: Fix checkout total calculation
+This title will be displayed in the dashboard navbar, so keep it short and descriptive.`,
   },
 
   brainstorm: {

package/cli/orchestrator.mjs

@@ -146,6 +146,13 @@ export async function runOrchestrator({
   const intakeResult = await spawnAgent("Jane", jane, "intake");
   state.phaseSummaries.intake = summarizeResults([intakeResult]);
 
+  // Extract short title from Jane's intake (SESSION_TITLE: ...)
+  const titleMatch = intakeResult.rawOutput.match(/SESSION_TITLE:\s*(.+)/);
+  if (titleMatch) {
+    const shortTitle = titleMatch[1].trim().slice(0, 60);
+    emit({ type: "session:update", title: shortTitle });
+  }
+
   // ===========================
   // PHASE 2: BRAINSTORM (parallel, 3-5 rounds)
   // ===========================

package/cli/stream-parser.mjs

@@ -84,6 +84,12 @@ export function createStreamParser({ teamNames, callbacks }) {
               callbacks.onSessionUpdate?.({ taskId: taskIdMatch[1] });
             }
 
+            // Detect short title from Jane
+            const titleMatch = text.match(/SESSION_TITLE:\s*(.+)/);
+            if (titleMatch) {
+              callbacks.onSessionUpdate?.({ title: titleMatch[1].trim().slice(0, 60) });
+            }
+
             const textLines = text.split("\n");
             let i = 0;
             while (i < textLines.length) {

package/cli/team.mjs

@@ -239,8 +239,11 @@ export async function runTeam(taskId, opts = {}) {
         console.log(`  ${success ? "✓" : "✗"} ${summary}`);
         vizSend({ type: "tool:result", success, summary });
       },
-      onSessionUpdate({ taskId: newTaskId }) {
-        if (createTask) {
+      onSessionUpdate({ taskId: newTaskId, title: newTitle }) {
+        if (newTitle) {
+          vizSend({ type: "session:update", title: newTitle });
+        }
+        if (newTaskId && createTask) {
           taskId = newTaskId;
           if (tracker === "linear" && config.linear?.workspace) {
             taskLink = `https://linear.app/${config.linear.workspace}/issue/${newTaskId}`;
@@ -251,7 +254,7 @@ export async function runTeam(taskId, opts = {}) {
             if (repo) taskLink = `https://github.com/${repo}/issues/${newTaskId}`;
           }
           console.log(`\n  # Task: ${newTaskId}${taskLink ? ` (${taskLink})` : ""}\n`);
-          vizSend({ type: "session:update", taskId: newTaskId, taskLink, title: description || newTaskId });
+          vizSend({ type: "session:update", taskId: newTaskId, taskLink, title: newTitle || description || newTaskId });
         }
       },
       onSessionEnd({ duration, steps, inputTokens, outputTokens }) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kendoo.agentdesk/agentdesk",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "AI team orchestrator for Claude Code — run collaborative agent sessions from your terminal",
   "type": "module",
   "bin": {

package/prompts/team.md

@@ -359,6 +359,11 @@ Based on what you find, Jane determines the starting point:
 - Branch exists but no PR: Review what's implemented, continue from EXECUTION.
 - PR exists: Review the PR status, continue accordingly.
 
+IMPORTANT: At the end of the intake, Jane MUST provide a short title for this session on its own line in this exact format:
+SESSION_TITLE: <4-8 word title>
+Example: SESSION_TITLE: Fix checkout total calculation
+This title is displayed in the dashboard navbar, so keep it short and descriptive.
+
 ---
 
 ## BRAINSTORM (3-5 rounds)