Conversation unification (FAB thread = record folder thread)¶
| Stage | Estimated |
|---|---|
| Status | Deferred |
| Design status | In review |
| Estimate | 1w (M) |
| Confidence | Medium |
| Linear | PIN-725 ↗ PIN-852 ↗ PIN-924 ↗ |
| Linear status | Done · +1 planned |
| Cycle | C15 |
| Design | Design ↗ |
| Linear epic | Cara AI & Automation |
| Module | Cara ↗ |
Status check: deferred, but shipped work exists
This surface is marked deferred, yet Linear shows PIN-725 and PIN-924 as Done. Confirm whether it actually shipped (move the status off deferred) or only the remaining scope is deferred. Flagged for reconciliation.
Priority: High
Scope¶
Unify the FAB floating-chat thread with its record/project folder thread so the same conversation follows the user across surfaces: a per-project folder structure with chats auto-assigned to the right project, "Full page" resuming the exact active thread instead of a blank welcome screen, and the completion indicator surfacing the actual finished thread regardless of which page it's opened from. (Source: PIN-725, PIN-852, PIN-924.)
Acceptance criteria¶
- Cara workspace has a per-project folder structure; chats about a project auto-assign to that project's folder
- Project artifacts (e.g. a presentation in progress) are stored inside the matching project folder
- "Full page" link from the floating panel opens the exact active conversation, not a blank welcome screen
- Falls back to the welcome screen only when no thread is active yet
- The completion indicator on the Cara widget leads to the actual finished response, not an unrelated thread
- The indicator doesn't clear until the user has actually seen the completed message
Conor's comments¶
Would like the the full Cara workspace and AI integration built
Notes¶
Fixes shipped /cara↔FAB split
Open question for Conor¶
-