You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7f5e47e
Browse filesBrowse the repository at this point in the historyBrowse files
feat: enhance delegation handling and placement enforcement
- Updated `buildDelegationPreamble` to improve isolation messaging and authority of owner placement choices.
- Modified `useChatSessions` to include `checkoutPath` for better session management.
- Enhanced `useComposerSend` to handle pending sends and cancellation more effectively.
- Introduced `useDelegatedThreads` to enforce delegation placement rules, ensuring shared children respect owner choices.
- Added `useDelegationPlacement` to manage session placement choices before sending requests.
- Implemented new tests for delegation placement and compaction policies to ensure robust functionality.
- Created shared utilities for handling chat artifact frames and image file validation.
- Updated styles for better UI presentation of context usage details.
- Adjusted Vitest configuration to include TypeScript files in test patterns.
files open in the app with fit, zoom, actual size, dimensions, and reload. Image
5
+
editor tabs are read-only; desktop/web/Hub use the typed workspace client and SSH
6
+
uses SFTP binary reads. See [In-app image viewing](image-viewer.md).
7
+
3
8
Desktop system-tray behavior is opt-in through **Settings → General → Keep running in background**. Enabling it creates an OS tray with explicit **Open CrewCode** and **Quit CrewCode** actions; closing the window hides it without stopping terminals or agents, while tray Quit follows the normal cleanup path. Windows and Linux also restore on tray click (Linux StatusNotifierItem Activate is typically a single click). Disabling the preference removes the tray immediately. macOS retains its Dock icon, and web/Hub/headless runtimes never emulate the tray. See `docs/system-tray.md`.
4
9
5
10
Real agent integration is wired through normalized bridges (pi, OpenCode, Claude, Codex, Hermes, CrewCoder, Ollama, and OpenRouter) with PTY panes remaining available for terminals.
@@ -186,7 +191,7 @@ Inactive standalone terminal tabs remain mounted for PTY/process continuity, but
186
191
187
192
Idle refreshes follow the same responsiveness contract. The five-second prompt/skill/command scan is App-owned, so unchanged content must preserve the prior library object and slow scans must stay single-flight; local scan reads use asynchronous filesystem APIs rather than blocking Electron main. The automatic GitHub poll must use asynchronous, bounded child processes and preserve the prior App state for an unchanged result. Never add `spawnSync`, `readdirSync`, `statSync`, or `readFileSync` to an interval-, focus-, or visibility-driven status path. See `docs/terminal-stream-performance.md`.
188
193
189
-
Structural message updates (tool calls and new thinking blocks) must stay isolated from the workspace shell. `Messages`' `areRowsEqual` compares a work-log anchor's actual source `ToolCallMessage` identities; never replace that with blanket live-turn invalidation, because a growing thinking/text sibling would rebuild every work log in the turn. Agent rows receive a precomputed `showTurnSummary` boolean instead of reading the whole transcript. Self-contained rows — `thinking` above all — re-render only when their own message changes. `chronologicalStreamSegments` caches splits per chunk string, so a growing block only re-splits its tail instead of every chunk on every flush (that was quadratic in turn length); it also appends units in a loop rather than `push(...units)`, which throws on very long blocks. Solo-chat auto-follow runs in the next animation frame, not `useLayoutEffect`: reading `scrollHeight` synchronously during every React commit forced shell-wide layout. Keep `.thread-shell` layout/paint-contained so transcript reflow cannot invalidate the workspace drawer.
194
+
Structural message updates (tool calls and new thinking blocks) must stay isolated from the workspace shell. `Messages`' `areRowsEqual` compares a work-log anchor's actual source `ToolCallMessage` identities; never replace that with blanket live-turn invalidation, because a growing thinking/text sibling would rebuild every work log in the turn. Agent rows receive a precomputed `showTurnSummary` boolean instead of reading the whole transcript. Self-contained rows re-render only when their own message changes. Solo chat aggregates thinking and tools separately per turn; grouped anchors compare source identities so only changes to their own log invalidate them. Solo Thinking logs start open during active turns while Work logs start closed and remain manually expandable; both collapse at observed turn completion, and load closed in completed history while remaining manually expandable, without header dividers; history paging retains complete visible turns. `chronologicalStreamSegments` caches splits per chunk string, so a growing block only re-splits its tail instead of every chunk on every flush (that was quadratic in turn length); it also appends units in a loop rather than `push(...units)`, which throws on very long blocks. Solo-chat auto-follow runs in the next animation frame, not `useLayoutEffect`: reading `scrollHeight` synchronously during every React commit forced shell-wide layout. Keep `.thread-shell` layout/paint-contained so transcript reflow cannot invalidate the workspace drawer.
190
195
191
196
`ChatPane` is still not `React.memo`'d, but that is now a cost/benefit call rather than a correctness trap: `MessageRow` is already memoized and `Messages` pages at 50 rows, so an App-driven ChatPane re-render is cheap reconciliation. Memoize only against a profile, never against a theory.
0 commit comments