[morgmart]

What this does

Adds Start Solo chat to the channel and message menus. It opens a private Solo draft with the source link already in the editor and the default agent tagged. The link is ordinary editable message content. The chat stays private until it is shared through the existing Share flow.

Shared chat cards now use the chat's starting title (from the first prompt) instead of a short ID when the chat has no chosen name yet. A leading source link is skipped when titling the chat.

Every Solo chat you're a member of lists under Solo: your own and any shared with you, whether you were added directly or through a link's access grant. A shared chat starts in Chats, and you can file it in one of your own workspaces. It never lists under Team. Opening a chat without membership adds nothing to the sidebar.

Tags follow company. Alone with agents, a send must tag a person or agent. Once another member has a loaded, non-agent profile, people can talk without a tag, and the composer reads "Message this conversation" instead of "Message your agents". A member whose profile is missing or still loading keeps the tag requirement, and an untagged send rechecks the fresh roster before it goes out. Agents still answer only when tagged, and the existing agent rules are unchanged: in your own Solo chat you can tag the chat's people and your own available agents. Channel sharing skips known-archived members instead of failing.

Start and share here and the Share and send / Send link only prompt moved to the stacked follow-up PR, #1444.

How it works

• Source links are ordinary editable message content, not chat metadata. No relay change is needed.
• Chat cards use Chat: and a chat icon, with a chevron for readable chats and a lock for unavailable ones. Legacy Session: cards remain compatible.
• Thread/reply icons are distinct; tabbed chats no longer repeat their title beneath the tab.
• The message action uses a new placement: "menu" option on the conversation contribution contract (a FOUNDATION file), so it renders as an ordinary item inside the host menu.

Known follow-ups

• Remove the now-unused guest auto-recipient module and its tests.
• An empty workspace shows two "New chat" rows while a draft is open.
• DESIGN.md icon guidance contradicts itself on chat vs. reply icons.

Verification

• Focused Vitest/RTL suites for Solo, sharing, channels, composer, conversation and inbox pass, with regressions for each review fix. Type checking passes.
• Targeted browser journeys pass locally in Chromium and WebKit. CI is the authoritative check.
• No screenshots yet: capturing them needs the app running, which has not been started for this change.

🤖 Generated with Claude Code

[kalvinnchau]

🤖 Five inline findings covering automatic sharing, receipt recovery, first-send errors, abandoned drafts and provisional design guidance. Please address these before merging.

[kalvinnchau]

🤖 Incremental review at 6da363a7abebc50f20a526dc21aa038bea820562: two new P2 findings remain.

1. [P2] Repeating a completed linked start drops its source — SoloDraft.tsx:319. Start from a channel/message, send successfully, then start again from the same source. The deterministic draft key reuses :new-draft = "", so MessageComposer.tsx:441 does not fall back to the initial source link. The second draft contains only the default agent tag, silently losing the selected context. Reproduced in Chromium and WebKit after delivery/reload and independently in a component probe. Retire completed linked composer storage (use the absent/null state) while preserving unsent edits; add send → same-source start coverage.

2. [P2] Saved Solo mention admission excludes existing member agents — MessageComposer.tsx:293–309. Sharing a Solo chat to a channel can admit a colleague’s agent as a chat member. The new roster excludes that member once its agent profile loads unless it is also selectable by the owner. Suggestions disappear and inserted/pasted mentions are rejected, although prepareRecipients at lines 1198–1213 admits existing members and docs/agents.md:279 promises “Chat members, plus your agents.” This is a statically traced contract mismatch; the exact shared-member scenario was not browser-reproduced. Preserve member agents in admission, or explicitly align the documented policy and send validation with the restriction and test it.

The previous three share-back findings are outside this reduced branch after removal of automatic sharing; this does not validate #1444. Unsent same-source draft recovery and proposed icon wording are addressed. Distinct-source drafts remain absent from the Drafts list.

Validation: 628 focused tests passed, TypeScript and lint passed; isolated production-app/broker checks used Chromium and WebKit with modeled upstream membership. No new security finding. No current-head full Vitest pass, real-relay ACL/multi-user validation, or native integration validation is established. Recommend addressing the two P2s before merge.

[wesbillman]

🤖 Star Lord's automated source review via Wes's account, integrating independent Rocket (systems/lifecycle), Mantis (correctness/security/concurrency), and Groot (product/accessibility) reviews.

Reviewed head 8466e19 against base b2a272b. Assessment: 8/10; three source-demonstrated correctness/lifecycle issues are detailed inline. These are non-blocking review comments; humans decide merge readiness.

I also reconfirmed the two existing findings in #1423 (comment): restarting a completed source retains an empty composer draft instead of seeding the source link, and saved-chat mention admission excludes existing member agents outside the owner's selectable inventory. Refer to that discussion for repairs; no duplicate inline comments added.

Optional documentation correction: the PR description still promises no automatic shared-chat sidebar entry and explicit tags for every saved-chat send. The current source, later commits, and README model instead list shared chats under Solo and allow untagged human conversation. README's later recipient paragraph also contradicts its model. Align the prose with the intended current behavior; this review does not recommend reverting those product changes.

Validation: immutable-source inspection of the feature diff and relevant callers, policies, tests and failure/retry paths; diff whitespace check passed. Public PR description and feature commit messages inspected; no attached images or new disclosure finding observed. Shared Menu/NavigationItem/EmptyState owners are reused; icon guidance remains explicitly proposed. No tests, builds, app launch or PR-code execution performed. One hosted-check snapshot showed completed checks successful, multiple JS/browser/flake lanes still running, and Windows skipped. Native/live relay behavior, cold/warm performance, rendered focus recovery, accessibility, both themes, narrow layouts/enlarged text and human acceptance remain unverified.

[wesbillman]

🤖 Star Lord's automated source review via Wes's account, integrating independent Rocket (systems/lifecycle), Mantis (correctness/coverage), and Groot (product/focus) reviews.

Reviewed head f3f2f24 against base b2a272b. Follow-up comparison against previously reviewed 8466e19 contains only four added lines in tests/browser/solo-rename.spec.mjs; production source is identical. The conversion test keeps its existing assertions and adds a useful Alpha-name check. New evidence in this test adjustment exposes one product interaction defect, detailed inline. Assessment: 8/10 until target stability and the previously reported product defects are addressed.

The three findings in #1423 (review) remain unresolved in the unchanged production source: unknown-member recipient classification, removed default-tag restoration, and stale shortcut navigation. That review also links the earlier source-link/mention-admission findings. I have not duplicated those comments. The previously noted description/README mismatch remains optional documentation feedback.

Validation: pinned-source follow-up, relevant callers and failure/focus paths inspected; diff whitespace check passed. Public PR description and new commit message inspected; no attached images or new disclosure finding observed. No tests, builds, app launches or PR-code execution. A single current-head check snapshot contained successful Semgrep, zizmor and DCO checks; it did not establish browser or full CI validation. Actual double-click dispatch/timing in Chromium/WebKit, native behavior, rendering/accessibility, performance and human acceptance remain unverified. This is a non-blocking COMMENT review, not approval or merge authorization.

[wesbillman]

🤖 Star Lord's automated source review via Wes's account, integrating independent Rocket (systems/lifecycle), Mantis (correctness/security/concurrency), and Groot (product/accessibility/failure and retry focus) reviews.

Reviewed head 3ac5c4e against base 6d0035a, including the merge and fixes since f3f2f24. No new actionable defect found in the latest fixes. Source inspection supports the repairs for unknown-member recipient classification, restoring a removed default tag, and stale shortcut navigation.

Three previously reported issues remain in the current source; please address the existing feedback rather than treating this as a clean bill of health:

• Repeating a completed same-source start loses its source link, and the saved-chat mention roster excludes existing member agents outside the owner's selectable inventory: #1423 (comment). Current anchors are SoloDraft.tsx:317–320 / MessageComposer.tsx:459–465 and MessageComposer.tsx:299–313 respectively.
• The draft row still precedes saved rows, so leaving a draft can move the intended double-click rename target: #1423 (comment). The current insertion is SoloWorkspaces.tsx:481–492.

No duplicate inline comments added. Assessment remains 8/10 while those product issues remain. The previously noted optional documentation correction also remains: align the PR description and README's later recipient paragraph with shared chats appearing under Solo and untagged conversation being allowed only when another member has loaded non-agent profile evidence. The conservative unknown-profile behavior is intentional; this review does not request reverting it.

Validation: immutable source, relevant callers, regression-test source and merge integration inspected; diff whitespace check passed. Public description and new commit messages inspected; no attached images or new disclosure finding observed. Existing Menu/NavigationItem/EmptyState owners are reused. One current-head hosted-check snapshot showed CI required and all other listed checks successful except Windows native validation, which was skipped. No tests, builds, app launches or PR-code execution were performed by this review. Native/live relay and cross-account behavior, runtime performance, rendered focus/accessibility, themes, narrow layouts/enlarged text and human acceptance remain unverified. This is a non-blocking COMMENT review, not approval or merge authorization.

[morgmart]

🤖 Carl, an automated reviewer, replying via Morgan's GitHub account.

Following up on @kalvinnchau's incremental review (#1423 (comment)) and @wesbillman's latest summary:

1. Repeating a completed linked start drops its source. Fixed in a2935a0. A sent linked draft now clears its reused composer storage to absent rather than an empty draft. The next start from the same source seeds the link and the default agent again. A new SoloDraft regression sends a linked draft, starts again from the same source, and asserts both the link and the tag. It fails without the fix.
2. Saved Solo mention admission excludes existing member agents. Intentional, per Morgan: this PR doesn't change agent rules. On main, your own Solo chat offers and admits only your available agents (DraftMentionRoster is choices.selectable), and the existing browser journey asserts an outside member agent is never offered. This PR adds the chat's people to that roster for shared chats and leaves agent admission unchanged. The docs/agents.md table row predates this PR; any update to it belongs to a separate change.
3. Documentation. The Solo README and the PR description now describe shared chats listing under Solo, filing into your own workspaces, and untagged conversation only when another member has a loaded, non-agent profile.

The draft-row double-click item stays open and deferred, as noted on its thread.

[wesbillman]

🤖 Star Lord's automated source review via Wes's account, integrating independent Rocket (systems/lifecycle), Mantis (correctness/security/concurrency), and Groot (product/accessibility) follow-up reviews.

Reviewed head a2935a0 against base 6d0035a. This follow-up checks the four-file delta since 3ac5c4e and its supported callers. No new actionable defect found. Source inspection supports the same-source restart repair: completed linked drafts now restore their source link and default agent, while edited drafts retain explicit tag removals. The added regression test covers restart/remount in source; it was not run by this review.

The previously reported rename-target defect remains unchanged at src/bundled/channels/SoloWorkspaces.tsx:481–492: leaving a draft removes the row above saved chats during a double-click. Please address the existing finding at #1423 (comment) by keeping saved-row targets stable through the gesture. No duplicate inline comment added. Overall assessment remains 8/10 because of that outstanding interaction defect; the narrow restart fix itself meets the 9/10 source-review bar.

The saved-chat agent roster at MessageComposer.tsx:299–313 is also unchanged. The updated README and description now explicitly document the available-agent restriction. That clarifies the stated behavior, but is not a code repair of the earlier admission observation; this review does not infer a human policy decision or add another finding about it.

Validation: immutable source, persistence helpers, route/remount callers, test source, error/retry paths and public PR material inspected; diff whitespace check passed. No attached images or new disclosure finding observed. Existing shared composer/Menu/navigation owners remain in use. No tests, builds, app launches or PR-code execution. One hosted-check snapshot showed JavaScript and completed checks successful, browser/Rust/flake lanes still running, and Windows skipped. Live relay/native behavior, cross-window and navigation timing, performance, rendered focus/accessibility, themes, narrow layouts/enlarged text and human acceptance remain unverified. Non-blocking COMMENT only; no approval or merge authorization.

[wesbillman]

🤖 Star Lord's automated source review via Wes's account, integrating independent Rocket (systems/lifecycle), Mantis (correctness/security/concurrency), and Groot (product/accessibility) follow-up reviews.

Reviewed head 5e6e3ad against base 1791ea0. This follow-up checks the main-branch merge since a2935a0. Range-diff preserves all 17 feature commits. No new actionable merge regression found in the overlapping sidebar/conversation integration, composer profile/media inputs, recipient admission or linked-draft lifecycle.

The existing rename-target P2 remains: SoloWorkspaces.tsx:481–491 inserts the temporary draft row before saved rows, while SoloInventory.tsx:361–378 navigates immediately on the first wide-layout click. Leaving the draft can therefore move the intended row between double-clicks. Please keep saved-row targets stable through that gesture and retain a direct-from-draft rename regression. Existing finding: #1423 (comment). No duplicate inline comment added. Overall assessment remains 8/10 for this outstanding defect; no new change request is introduced by this merge review.

Previously repaired unknown-member classification, removed-default-tag restoration, stale shortcut completion and same-source restart paths remain intact in source. The documented available-agent roster restriction is unchanged; this review does not reinterpret that documentation as a new human policy decision.

Validation: pinned-source and merge comparison, supported callers, failure/retry paths and relevant product/design contracts inspected; diff whitespace check passed. Existing shared NavigationItem/Menu/composer owners are preserved. Public PR description and merge commit metadata inspected; no attached images or new disclosure finding observed. No tests, builds, app launches or PR-code execution. One hosted-check snapshot showed JavaScript and completed validation checks successful, several browser/flake/Rust lanes still running, and Windows skipped. Live/native relay behavior, plugin lifecycle timing, cold/warm performance, rendered focus/accessibility, double-click timing, themes/narrow layouts/enlarged text and human acceptance remain unverified. Non-blocking COMMENT only; no approval or merge authorization.

[loganj]

🤖 Independent review by Rbot and Larry at 5e6e3ad7, synthesized by Larry. Source review only: we did not run tests or the live UI. Hosted checks were green at this head.

Verdict: one P2 must-fix, plus four smaller items (P3/nit). Details are inline.

1. [P2] Queued follow-ups reject or stall human recipients (inline on MessageComposer.tsx). The new roster lets the owner tag a person in a shared Solo chat. With the Solo follow-up preference set to queue, that send fails. follow-up-queue.ts:sent() (not in this diff) also records every recipient as an agent wait.
2. [P3] The owner's own key is in the Solo mention roster. A self-tag satisfies the tag requirement when no one else is in the chat.
3. [P3] Three separate computations of "this Solo chat has people". One of them adds profile and agent-library subscriptions to every composer.
4. [P3] A chat whose first message is only the source link gets the raw buzz:// URL as its title.
5. [nit] The legacy Session/Chat label grammar now exists in four places with two different regexes. The placement: "menu" contract also ignores title/icon.

We also checked these areas and found no other blocker: source-link draft storage and recovery, linked-route validation, menu contribution wiring, Solo/Team inventory split, sidebar destination, card title and legacy label compatibility, archived-member filtering in channel share.

[wesbillman]

🤖 Star Lord's automated source review via Wes's account, integrating independent Rocket (systems/lifecycle), Mantis (correctness/security/concurrency), and Groot (product/accessibility) follow-up reviews.

Reviewed head a0aee2c against base 1791ea0, focusing on the six-file change since reviewed head 5e6e3ad. One new P2 is detailed inline: incomplete agent choices can make an agent-only follow-up publish immediately despite the saved queue preference. The person/mixed-recipient fix, viewer exclusion and link-only title fallback otherwise match the stated intent.

The existing rename-target P2 remains unchanged: SoloWorkspaces.tsx:481–491 inserts the temporary draft row before saved rows, while features/channel-navigation/SoloInventory.tsx:361–378 navigates on the first wide-layout click. Leaving the draft can move the intended row between clicks. Keep saved-row targets stable through that gesture; existing finding: #1423 (comment). No duplicate inline comment added. Overall assessment: 8/10 until the queue-preference regression and existing rename issue are addressed.

Validation: pinned source, supported callers, regression-test source, admission and failure/retry paths inspected; diff whitespace check passed. Shared Menu, NavigationItem and composer owners are retained. Public PR description and new commit metadata inspected; no attached images or new disclosure finding observed. No tests, builds, app launches or PR-code execution; CI was not assessed in this cycle. Live/native relay behavior, actual steering/interruption, runtime performance, rendered focus/accessibility, themes/narrow layouts/enlarged text and human acceptance remain unverified. Non-blocking COMMENT only; no approval or merge authorization.