osborn 0.9.24 → 0.9.25

package/dist/config.js

@@ -649,25 +649,24 @@ export async function listAllClaudeSessions(limit = 100) {
             ]);
             if (preview.messageCount < 2)
                 continue;
-            // SLUG-FIRST: prefer the slug-derived path over the content cwd.
+            // SLUG-FIRST for both `cwd` (routing) and `projectPath` (display).
             //
-            // Claude Code's `--resume <id>` looks up sessions by file LOCATION
-            // (slug folder under ~/.claude/projects/), not by the cwd field inside
-            // the JSONL. The JSONL content cwd is immutable historical metadata —
-            // it's where the session was ORIGINALLY recorded (e.g. sprite path
-            // /home/sprite/workspace or /workspaces/codespaces-blank). On migration
-            // (sprite → fly), files were finalized into a new slug but their
-            // content still records the original cwd.
+            // The workspace root (the agent's cwd, e.g. `/workspace` on fly) is
+            // the base layer. Projects are subdirectories beneath it — a session
+            // started in `/workspace/instagram` gets slug `-workspace-instagram`,
+            // and slugToPath turns that back into `/workspace/instagram`. The
+            // dashboard groups by this path → "instagram" naturally becomes a
+            // project card. Sessions started at the workspace root collapse into
+            // one "General" / "Workspace" card.
             //
-            // The dashboard forwards this field as `workingDirectory` to the
-            // agent, which uses it as Claude Code's spawn cwd. If it doesn't
-            // match the slug, the spawn lands in the wrong folder and resume
-            // errors with "No conversation found". The slug is the source of
-            // truth for where the file lives on disk; use it.
-            //
-            // Content cwd is kept as a last-resort fallback only when slug
-            // reversal fails (slugToPath validates with existsSync and returns
-            // '' on ambiguous encodings like dir names containing literal '-').
+            // Why NOT prefer the content cwd: the JSONL records whatever cwd
+            // existed when the session was recorded — for migrated sessions that
+            // can be a path that no longer exists on this host (e.g.
+            // `/workspaces/codespaces-blank` from someone's Codespace). Using
+            // file LOCATION as the source of truth keeps grouping aligned with
+            // where the data actually lives and where Claude Code's --resume
+            // will look. Content cwd is kept as a last-resort fallback for the
+            // rare case where slugToPath reversal fails.
             const slugPath = slugToPath(c.slug);
             sessions.push({
                 sessionId: c.sessionId,

package/dist/index.js

@@ -164,6 +164,14 @@ function startApiServer(workingDir, port) {
                 const limit = parseInt(url.searchParams.get('limit') || '100', 10);
                 const sessions = await listAllClaudeSessions(limit);
                 const payload = {
+                    // The agent's working directory at launch — the BASE LAYER of all
+                    // project organization. The dashboard groups sessions relative to
+                    // this path: a session whose cwd === baseCwd is a "Workspace"
+                    // session (the base); a session at `${baseCwd}/<name>` is a
+                    // project called "<name>". Replaces the dashboard's previously-
+                    // hardcoded base-path list — agent self-describes its base so
+                    // the UI doesn't have to keep a sync'd copy.
+                    baseCwd: workingDir,
                     sessions: sessions.map(s => ({
                         sessionId: s.sessionId,
                         projectSlug: s.projectSlug,
@@ -3100,6 +3108,11 @@ async function main() {
                     const sessions = await listAllClaudeSessions(100);
                     await sendToFrontend({
                         type: 'sessions_list',
+                        // See `/sessions` HTTP handler — baseCwd is the agent's
+                        // workingDir, the base layer the dashboard groups against.
+                        // Sent here too so the in-chat session list grouping stays
+                        // consistent with the dashboard's grouping.
+                        baseCwd: workingDir,
                         sessions: sessions.map(s => ({
                             sessionId: s.sessionId,
                             projectSlug: s.projectSlug,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "osborn",
-  "version": "0.9.24",
+  "version": "0.9.25",
   "description": "Voice AI coding assistant - local agent that connects to Osborn frontend",
   "type": "module",
   "bin": {