[AbirAbbas]

Summary

A conversation can now be told only about its own work. Today every conversation in a folder gets an <elsewhere> block with the other conversations' landed and running work there (with the files each wrote), and its tasks tool lists the folder's whole task index. A client that keeps a long-lived conversation in a person's shared work folder needs that conversation to see only its own work while keeping its folder, transcript and history.

• session.Meta.Scope: conversation, or absent for project (today's behaviour). Written by session.SetConversationScope under the existing cross-process meta lock; the session's own stamps patch only their fields, so it survives them.
• Read beside the turn in refreshElsewhere and in the tasks tool (both already read disk), so a live conversation follows the stored word from its next turn with no remote-protocol change. Scoped: no <elsewhere> block; the tasks tool lists and addresses only this conversation's rows; no running-in-other-windows or everywhere sections. The person's @ list, task nodes and the write-safety warnings (ground shift, preflight) are unchanged.
• Wire: agents.set_scope {id, scope} → {id, scope}; hello feature agents.scope. It never opens, warms or interrupts the conversation (like agents.mark_seen). bad_params, not_found, conflict (lent conversation or no local folder), unknown_method on engines without the door.

Why a stored switch rather than moving a conversation to another folder: Config.Workspace is captured at launch and the session folder, task index, presence, told stamp and transcript URIs are keyed on it; a move would re-key all of them. A live in-memory dial would need new remote-protocol plumbing because app conversations are remote.Agent connections. The stored word is one field, one setter and two read sites. (The Workstreams plan, L-FIX9.)

Validation contract

Item	Behaviour	Test
A1	scoped conversation gets no <elsewhere> block despite another conversation's recent landing and running task	TestConversationScopeLeavesOtherWorkOutOfTurnContext
A2	its tasks tool lists/reads/steers/resolves only its own tasks; no other-window or everywhere sections	TestConversationScopeTasksReachOnlyItsOwnRows, TestConversationScopeKeepsItsLiveGraphWhileFilteringTheMergedIndex, TestConversationScopeLeavesATaskNodesChildrenVisible
A3	unset or project behaves exactly as before	TestProjectScopeKeepsOtherWorkVisible, TestConversationScopeDefaultsQuietlyToProject
A4	survives reload and later effort/title/spend/places stamps	TestConversationScopeSurvivesReloadAndLaterMetadataStamps
A5	an earlier block clears at the next reading	TestConversationScopeClearsAnEarlierBlockOnTheNextReading
A6	changes nothing else in meta.json or the transcript; repeat writes nothing	TestConversationScopeChangesOnlyItsStoredWord, TestConversationScopeStaysInMetaBesideSealedConversationSettings
A7	wire validation, hello gating, unknown_method, not_found, lent refusal, closed agent written without opening	internal/appwire/agent_scope_test.go, cmd/codeaf/appscope_test.go
A8	unknown word and folder without meta.json refused; never minted	TestConversationScopeRefusesUnknownWordsAndMissingConversations

Left for later

The scope is local meta.json state: it is not carried when a conversation moves to another computer.

🤖 Generated with Claude Code