[baxen]

Why

Me placement is stored only in the owner's encrypted groups:me record. A remote agent (kgoose) signs in with its own key, so it can't tell a Me chat apart from any other private session. It defaults to thread scope, and because every message in Me is top-level, each message starts a fresh session. Local agents get this right because meChat() reads the owner's placement; remote agents have nothing to read.

What

New Me chats add a personal line to the existing session description, which the relay already publishes in the channel's kind 39000 about tag:

Buzz session (buzz.sessions/v1)
[parent:<uuid>]
[personal]

The lines must appear in that order, each at most once, with nothing else allowed. sessionMetadata and the Tauri host validator (channel_writes.rs session_metadata) now share that grammar. Without the Rust change, the desktop host would refuse to sign the new kind 9007.

• Set: NewSessionComposer passes personal to workSessions.create.
• Cleared: direct Share already replaces a session description with the user's description (empty by default). It runs before Me placement is removed, so a chat moved to Messages never keeps the hint.
• Kept on rename: renaming a session sends a name-only kind 9002, so the line stays.
• Not access authority: this is a routing hint only. The relay doesn't enforce it, and signed membership stays the access authority. That fits the current baseline in docs/sessions/README.md; it doesn't revive the superseded relay-enforced spaces.md proposal.

Contract for remote agents: a channel whose 39000 about parses with a personal line is the owner's personal chat. Use one channel-scoped session and post at the top level, as meChat() does locally. The kgoose side is a separate change.

Not in this PR / decisions for review

• No backfill. Existing Me chats keep today's remote behavior (thread-scoped) until they're recreated or a one-time edit is added.

• Link share leaves the hint in place. Destination-link sharing grants other people access but leaves the chat in Me, so it keeps the hint. That matches what local agents do today (they follow placement). If link share should mean "no longer personal", it needs a follow-up.

• Version skew. Older app builds parse the session description exactly, so they show a new Me chat as an ordinary private stream:

  • the raw description is visible;
  • rename is blocked by the "Buzz session (" guard;
  • direct share from the old build requires editing the description first.

  This only affects people running several devices on different versions.

Testing

• vitest run: 615 files, 8824 tests pass, plus the new metadata grammar, 9007 creation, composer, rename and direct-share cases. When personal parsing is broken, 8 direct-share tests and the grammar test fail.
• cargo test --manifest-path src-tauri/Cargo.toml: 369 passed and 1 failed. The failure was host_command::tests::stdin_is_exact_data_and_output_is_drained_concurrently, which passed 3 of 3 times on its own, so it's a load flake unrelated to this change. The new creation_accepts_only_the_session_description_grammar test passes.
• tsc --noEmit, biome, clippy and pre-push hooks all pass.
• Not yet exercised in the native app: creating a Me chat and checking its 39000 about, then direct-sharing it and checking the line is gone.

🤖 Generated with Claude Code

[wesbillman]

🤖 Carl, an automated reviewer, commenting via Wes's GitHub account.

Fine as a bridge, but please make the kgoose side trust personal only when signed membership agrees: the owner is the only human and every other member is one of the owner's agents. Otherwise a shared channel that still has the line merges several people into one agent session.

Longer term I'd rather give the owner's agents read access to Me placement (for example, encrypted to their keys) than add more flags to the about text, since that keeps one private source of truth and covers existing chats without a backfill.

[wesbillman]

🤖 Carl, an automated reviewer, commenting via Wes's GitHub account.

Correction to my comment above. I'm withdrawing both suggestions:

• The membership check was wrong. meChat() only checks placement, so local agents already treat a link-shared Me chat as one channel-scoped conversation. This PR matches that on purpose, and the check would make remote agents behave differently from local ones. Editing about also requires channel owner/admin (the relay's 9002 authorization), so it isn't an open spoofing path.
• The drift concern was overstated. Placement is only written at creation (NewSessionComposer) and on direct Share (SessionShare), and this PR sets and clears the line at those same two points. The real gap is existing chats, which the PR already documents.

Sorry for the noise.