Repository navigation
feat(lazurio): Buddy's window over one thread of the shared server (R3) - #229
Conversation
…hared server The design is in the pull request; code follows on this branch. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rver (R3, server) T3CODE_LAZURIO_BUDDY_ORIGIN names Buddy's window's own origin beside the Buddy folder and reaches clients as lazurioBuddyOrigin. On a shared server the thread route answers the oldest root thread of Buddy's project, or makes one on the project's, the Environment's or the Lazurio project's model; the days route reads that thread; a message with a page record gets the page block on any provider. Buddy's own server (GEN3) keeps its paths. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…erver (R3, web) The web is in Buddy's surface on Buddy's own origin (lazurioBuddyOrigin) as well as on Buddy's own server; only Hermes's chat (GEN3) swaps the composer for Normal / Fast. A loopback http origin is accepted for development. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…r lines Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d effort shortcuts Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ad in Buddy's frame The coordinator decided (option B): in Buddy's window on the shared server the thread behaves as in Chat, with the right panel, the work of tools, rollback, /clear, side chats and the thread's details; Buddy keeps its frame, the days and the page chip, and the threads of Buddy's project (subagents, forks) open in the window. Hermes's quiet conversation and its limits stay GEN3's. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ad offers no Git setup Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…width, as in Chat Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s window Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
b710822 to
8bd9878
Compare
Buddy GEN4's entry.buddy names his window's origin where the lane keeps it, served by the shared T3 Code (R3, Lazurio/t3code#229), and no port of his own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Blocking:
useLeadsToBuddysThreadinapps/web/src/lazurio/BuddySurface.tsxredirects a directly opened or reloaded GEN4 fork/subagent thread to the root Buddy thread. On a fresh pagebuddyThreadIdis null, so the project check cannot pass and_chat.tsxmountsBuddySurfaceIndex, which navigates to the root even for a thread in Buddy’s project. Resolve the Buddy project before deciding, preserve the requested project thread, and cover a fresh load and reload.
Non-blocking: The required CI jobs passed. I could not run the local tests because dependencies are not installed; the browser and real-phone checks remain unverified.
Order and migrations: finish https://github.com/HumanAndMachine-ai/Machines/issues/1330 and the Platform integration before converting a person to GEN4; coordinate the release and canary separately.
— Pablo
|
@immakermatty Předávám vám dokončení PR: opravte přímé otevření a obnovení forků a vedlejších vláken podle review na commitu 8bd9878, ověřte chování v prohlížeči a požádejte o nové review přesného headu. Místní testy jsem kvůli chybějícím závislostem nespustil. — Pablo |
… load On a fresh page or a reload Buddy's thread id was not known yet, so the project check could not pass and the route led every thread of Buddy's project, forks and subagents included, to the root thread. The decision (leadsToBuddysThread) now takes Buddy's project from the server's Buddy folder (the unlisted project ids) and waits until the thread and that project are known; only another project's thread leads to Buddy's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Fixed in fa223db: a fork or subagent of Buddy's project now stays open when it is opened directly or the page is reloaded. Cause, as the review says: on a fresh page Fix: the decision is now the pure
Tests:
Live check: a dev server with separate data and Buddy's window on its own origin (
Checks: I'll ask for a new review on this head once CI is green. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Blocking:
- On a fresh GEN4 server with no threads, opening a missing thread URL in Buddy's window leaves a blank view.
leadsToBuddysThreadreturns false while the missing shell has no project ID;ThreadRouteViewnavigates home only whenenvironmentHasAnyThreadsis true. Thus/never runs to create and open Buddy's thread. Distinguish a confirmed missing thread from one still loading and route it to Buddy even when the server has no threads; cover that case.
Non-blocking: The previous finding about fresh-loading forks and subagents is addressed. The new head's CI is still running. Local tests could not run: vp and dependencies are absent; browser and real-phone checks were not performed.
Order and migrations: finish https://github.com/HumanAndMachine-ai/Machines/issues/1330 and the Platform integration before converting a person to GEN4; coordinate the release and canary separately.
— Pablo
Buddy GEN4's entry.buddy names his window's origin where the lane keeps it, served by the shared T3 Code (R3, Lazurio/t3code#229), and no port of his own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Buddy GEN4's entry.buddy names his window's origin where the lane keeps it, served by the shared T3 Code (R3, Lazurio/t3code#229), and no port of his own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…on an empty server On a fresh GEN4 server with no threads, a missing thread's address in Buddy's window left a blank view: the route waited for a project that the missing thread never has, and Chat's own redirect home runs only where the environment has threads. The window now takes the route's own "missing" (resolveThreadRouteRenderState over the shell status and the thread's detail) and leads such a thread to Buddy's, which `/` then makes; a thread still loading still waits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Fixed in e43d3f2: on a GEN4 server with no threads, a missing thread's address in Buddy's window now opens Buddy's thread. Cause, as the review says: the window waited for the thread's project. A missing thread never has one, and Fix:
Tests:
Live check: a fresh dev server with separate data and no thread, Buddy's window on
Checks:
I'll ask for a new review on this head once CI is green. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972 |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Blocking: None. The previous finding is resolved: a confirmed missing thread now leads to Buddy’s thread even on an empty server, while a thread still loading waits.
Non-blocking: CI is still running on this head. I could not run the local tests because vp and dependencies are absent; I did not independently verify the browser or a real phone. The author reports a successful isolated browser check for the empty-server case.
Order and migrations: finish https://github.com/HumanAndMachine-ai/Machines/issues/1330 and the Platform integration before converting a person to GEN4; coordinate the release and canary separately.
— Pablo
… (LZD-0033 R2) (#1072) * Buddy GEN4: AGENTS.md and skills of Buddy's folder, two profiles (LZD-0033 R2) Renders the coordinator's instructions for ~/Buddy (one AGENTS.md, no CLAUDE.md; each skill in .agents/skills and .claude/skills) in the profiles buddy and employee, with the persona from Settings → Buddy, and writes them into Buddy's folder under the Folder's lock. Not wired yet: the Folder starts writing it once the Machines handover carries entry.buddy.generation 4 (HumanAndMachine-ai/Machines#1330). Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread d27e5511-ab1d-4892-a9a9-0ec9646d4834 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: read entry.buddy.generation and write ~/Buddy for a converted person (LZD-0033 R2) The vendored lazurio.machine.v1 schema takes Buddy GEN4's member of entry.buddy (Machines#1398): generation 4, Buddy's folder and profile, the origin only while Buddy's own T3 is routed. The binding records buddyFolder and buddyProfile on a personal VM only, and every change of the Folder writes the Folder's sibling ~/Buddy with the persona instead of Buddy GEN3's layer, which is kept, not removed. Without the conversion nothing changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Folder: say where Buddy GEN4 lives on a converted person's Environment (LZD-0033 R2) Only where the binding records Buddy's folder: Buddy is a thread of the Buddy project in the shared T3 Code with ~/Buddy, Lazurio writes its AGENTS.md and skills, agents never edit them, and Buddy reads and watches the threads himself. Every other Folder renders the same bytes (the pinned digest of base-instructions-139 is unchanged); a person converted later gets the line through the rebound binding. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: answer a pending question elsewhere directly (pilot finding, LZD-0033 R2) The threads skill tells Buddy to answer a thread's pending question in another Environment himself, over the link with t3_pending_request or over SSH with t3 request list and t3 request respond, never through a handover thread. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: vendor Machines#1398's member without a port (LZD-0033 R2) Buddy GEN4's entry.buddy names his window's origin where the lane keeps it, served by the shared T3 Code (R3, Lazurio/t3code#229), and no port of his own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: refuse another home, a symlinked ancestor, CLAUDE.md and files of another account (LZD-0033 R2, review) - writeBuddyLocked writes the handover's buddyFolder only when it is exactly Buddy of the Folder's home, which must be its own canonical path and a directory of this account (buddyFolderTarget); a hosted Folder's home is its operator's, checked by bindMachineOperator. A mismatch, a nested path or a symlinked ancestor is refused and nothing is written. - An existing CLAUDE.md or .claude/CLAUDE.md in Buddy's folder is reported and kept, and nothing is written beside it. - inspectOutput refuses a file of another account in the whole Folder. - buddyGeneration(entry): 3 | 4 | undefined, the one rule for every reader. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: check ~/Buddy before the Folder change commits; tests through init and refresh (LZD-0033 R2, review) checkBuddyLocked runs before the initialization's and the change's transaction: another home, a symlinked ancestor, a CLAUDE.md or an unsafe file in ~/Buddy refuses the operation with the Folder, its binding and its entry as they were, so a retry after the fix sees the change anew and the Launchpad's restart follows. The binding records buddyFolder as an absolute, normalized path ending in /Buddy (the handover's schema keeps /home/<user>/Buddy), which lets the tests convert a Folder in a temporary home through initializeMachineFolder, refreshMachineFolder and refreshMachineFolderAndLaunchpad. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: writeBuddyLocked checks ~/Buddy itself before writing (LZD-0033 R2) A caller outside a Folder change, such as a change of the persona, is refused before anything is written, as a change is. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: the check before the change uses the writer's directory rule; a late failure still restarts the Launchpad (LZD-0033 R2, review) checkOutputDirectories applies ensureOutputDirectories' own rule (a real directory of this account on the folder's filesystem) to every existing directory on an output's way, without creating anything, and checkBuddyLocked runs it for each of Buddy's files. A failure the check cannot foresee after the change is recorded, such as a directory that does not let the account write, still restarts the Launchpad on the new entry in refreshMachineFolderAndLaunchpad; the failure is reported as it was and the next refresh writes the folder. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Machine schema: pin Machines#1398's merge commit d114214f (LZD-0033 R2) The vendored bytes are unchanged; only the provenance names the merge commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Format output-directories (biome) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Folder refresh: a late failure reports the Launchpad restart's result (LZD-0033 R2, review) When a refresh fails after the Folder recorded a new entry, refreshMachineFolderAndLaunchpad restarts the Launchpad on it and throws RefreshFailedAfterEntry: the original failure with `launchpad` restarted, restart-failed or not-supervised, as a successful refresh reports it. That a failed restart is not retried by a later refresh is the same for a successful refresh and is tracked in #1082. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: a late write of ~/Buddy is reported in the answer, a refusal is blocked (LZD-0033 R2, review) A write of Buddy GEN4's folder that fails after the Folder's change is recorded no longer throws: initialization and every refresh answer it in "buddyFolder": {"state":"failed","error"}, the change and its entry stand, the Launchpad restarts on them as after any refresh (its result in "launchpad"), the exit code stays the refresh's, and the next refresh writes ~/Buddy again. A refusal found before anything changed is BuddyFolderRefused, which the machine command answers as blocked with exit 2 and its reason (buddy-folder-mismatch, buddy-folder-claude-md, buddy-folder-unsafe) instead of an internal failure. RefreshFailedAfterEntry is gone with the throw. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Buddy GEN4: an owed Launchpad restart is made on retry; late refusals and update report (LZD-0033 R2, review) - The Launchpad's health answer reports the digest of the entry it started with (entryDigest). refreshMachineFolderAndLaunchpad restarts the supervised Launchpad also when the Folder is unchanged but the Launchpad reports another entry than the recorded one, so a failed restart is made by the next refresh. An older Launchpad that reports none owes nothing. - writeBuddyLocked reports everything after the change, a refusal found by its own check included (a CLAUDE.md that appeared after the check before the change), as buddyFolder {state: failed, reason?, error}; only a lost lock stops the operation. - lazurio update reports a refresh whose ~/Buddy write failed as a failure with its reason, and neededRefresh asks the operator's refresh while a converted person's ~/Buddy lacks what the product renders, so the next update writes it again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Folder refresh: a failed Launchpad restart is kept as owed and retried, also by lazurio update (LZD-0033 R2, review) refreshMachineFolderAndLaunchpad keeps a failed restart as owed in the install base (update/launchpad-restart-owed.json, owner-only, written atomically) and the next refresh restarts it whatever the Launchpad reports of its entry, an older release or one that does not answer included; a restart that succeeds, or finds no unit, clears it. lazurio update reports a refresh whose restart failed as launchpad-restart-failed and runs the operator's refresh again while a restart is owed, even with the Folder current. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Folder refresh: the owed restart is recorded ahead and survives an unknown supervision (LZD-0033 R2, review) refreshMachineFolderAndLaunchpad records the restart as owed before the refresh, so no failure or interruption between the recorded entry and the restart can lose it, and clears it when none was owed or a restart succeeds or finds the Launchpad unsupervised. A debt that cannot be recorded blocks the refresh with launchpad-restart-unrecordable before anything changes. A service lookup that fails is no longer taken as unsupervised: the restart is restart-failed and stays owed until a lookup works. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * CLI: the owed-restart path never fails a machine invocation (LZD-0033 R2) Without an install base the machine command keeps no debt instead of failing before its usage check, so a wrong invocation still prints the help with exit 2 (tests/machine-context.test.ts). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Folder refresh: a restart debt survives overlapping refreshes (LZD-0033 R2, review) The owed restart carries the token of the attempt that recorded it. A refresh clears only the debt it recorded or found, never one recorded since, and every failed restart records its debt anew, so a refresh whose restart fails after an overlapping one succeeded still leaves its debt for the next refresh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Folder refresh: one restart lifecycle at a time per install base (LZD-0033 R2, review) refreshMachineFolderAndLaunchpad runs the debt, the refresh and the restart under one restart lock per install base (update/launchpad-restart, the Folder's kernel lock, released with its process); an overlapping refresh is blocked as folder-busy, which lazurio update retries. Under the lock the debt is recorded before the refresh and cleared only after a refresh that owes none or a restart that succeeded or found the Launchpad unsupervised, so no attempt can clear another's; the tokens of the previous scheme are gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Status: ready for review. The server and web parts are built, tested and checked live on separate data, on
main6b461503. The Machines follow-up is open and the Platform follows. The sign by Buddy's avatar comes as a separate PR once its interface is approved.Verification so far
buddySurfaceThread.test.ts: GEN4 makes one thread on the project's, the Environment's or the Lazurio project's model; two first visits make one thread; an existing pilot thread is adopted whatever its provider;no-projectandnot-buddy.managedFolderConfig.test.ts: the Buddy origin is accepted only beside a Buddy folder, as a bare HTTPS or loopback origin.buddyPrompt.test.ts: a page record gets the page block on any provider.buddySurfaceControls.test.ts: the window is recognised by its origin; a fork or subagent of Buddy's project stays open on a fresh load, and only another project's thread leads to Buddy's.check:changedpasses exceptAgentContextBudget, which fails the same way onmain(73c56da2). The allowlist gate simulation is clean.http://localhost:8220and Buddy's window onhttp://[::1]:8220(T3CODE_LAZURIO_BUDDY_ORIGIN), each origin with its own pairing:Decided since (coordinator, 2026-11-18)
/clear, side chats, the thread's details and the model shortcuts all behave as in Chat. Buddy keeps its frame, the days and the page chip. Hermes's quiet conversation and its limits stay GEN3's. Threads of Buddy's project (subagents, forks) open in the window. Done; the narrow right panel takes the whole width, as feat(web): a narrow window shows the rail only beside the open left panel #216 does for Chat.buddy.<slug>stays.Proposed, separate PR: a sign by Buddy's avatar (not built yet)
Asked for 2026-11-18, passed on by Buddy through the coordinator. The person wants to see by Buddy's avatar, on every Lazurio screen where it shows, that Buddy is waiting for them or has something new. They want to answer from any of those screens, as a clean design tied to the thread's status in T3 Code, with browser notifications on top.
waitingwhen a runtime request is pending, which clears when it is answered;failedfor a failed or server-interrupted last turn, a provider error, or a failed scheduled task bound to the thread, which clears after the next completed turn;answeredwhen the last turn completed afterlastVisitedAt, upstream's server-side read watermark, so nothing new is stored;quiet.The precedence is waiting, failed, answered. The reader shows
unavailablewhen it cannot ask.GET /api/lazurio/buddy/signal(orchestration:read) returns{version: 1, state, threadId, since, request: {kind} | null, startedBy}.t3 lazurio buddy signal --json [--follow]gives the same over the agent connection. The Launchpad runs one follower and serves the state to the shell, so the badge shows wherever the bubble does without the bubble reaching across origins.waitingandfailed, and onansweredonly for a turn the person started, from one tab. The desktop and mobile app (later) read the same versioned interface.Known difference
Goal
Buddy's next generation (plan LZD-0033, step R3) is one thread of the internal project "Buddy" on the shared Chat server (#214:
T3CODE_LAZURIO_BUDDY_FOLDER, the project is unlisted in Chat). Buddy's window, the Launchpad bubble that today frames a second T3 Code server (T3CODE_LAZURIO_BUDDY=1, providerbuddy/Hermes), opens that thread instead. The person picks the provider, model and effort as in any Chat thread, with no profiles and no Normal/Fast switch. The default is the Environment's T3 Code default model, and the person's choice stays. The window still shows and passes "where in Lazurio I am" (the page context), and the days list in its left panel works. A person who has not been converted keeps Buddy's second server and its surface unchanged.What exists (survey of
faae02aa, confirmed against73c56da2)isBuddySurfaceEnvironment(T3CODE_LAZURIO_BUDDY=1) feeds the command guards, the startup defaults (Codex and Claude off, one-shot), the linked-environments and checkpoint wrappers, the thread and days routes, andlazurioBuddyinserver.getConfig. The web swaps the whole app onlazurioBuddy(__root.tsx,_chat*.tsx,ChatView, composer, timeline).buddy. The thread id is fixed tobuddy, its model tobuddy/default, andisBuddyInstancedrives the prompt projection (buddyPrompt.ts: the page as a Czech block, no T3 instructions, onlyfast).managedFolder*.ts,unlistedProjects.ts).${buddyOrigin}/(Platformsrc/shell/buddy-protocol.ts). It accepts messages only from exactlybuddy.<slug>, and the frame accepts a parent only atlaunchpad|t3code|mausbot.<slug>.Design
1. Buddy's window is Buddy's origin, served by the shared server
The window keeps its own origin
https://buddy.<slug>.lazurio.io. For a converted person the Environment's gateway routes that origin tot3code.serviceinstead of the second server (Machines). The server learns it from a newT3CODE_LAZURIO_BUDDY_ORIGIN(HTTPS, no credentials, only together withT3CODE_LAZURIO_BUDDY_FOLDER). It accepts that origin besideT3CODE_EXTERNAL_ORIGINfor the session cookie, the WebSocket and CORS, and gives it to clients aslazurioBuddyOrigin.The web is in Buddy's window exactly when
location.origin === lazurioBuddyOrigin; on Chat's origin it is Chat. Why an origin and not a route such as/buddyon Chat's origin:event.origin === buddyOrigin,isShellBuddyOrigin,isBuddysOwnPage) and protocol v1 stay as they are;${buddyOrigin}/.2. Buddy mode is the project's, not the server's
lazurioBuddyFolder, the patternisBuddyThreadalready uses inmanagedFolderGuards.ts. The GEN4 pieces read only this. The GEN3 pieces stay behindT3CODE_LAZURIO_BUDDY=1unchanged, and none of the server-wide wrappers (startup defaults, linked environments, checkpoints) runs on the shared server.useBuddySurfaceModebecomes "GEN3 server (lazurioBuddy), or Buddy's origin (GEN4)". On Buddy's origin/opens Buddy's thread and any other thread route leads back there, as today. On Chat's origin nothing changes: the project stays unlisted and a direct link still opens the thread as a normal Chat thread.3. The one thread
For GEN4, Buddy's thread is the oldest root thread of the Buddy project that is not deleted. Archiving is refused, and threads archived earlier come back at startup (#214).
buddy, thebuddy/defaultmodel and the 409thread-conflictbelong to GEN3 only.t3 lazurio buddy thread --jsonanswers the same thread on the shared server.Why not a fixed id: the pilot's thread already exists with an ordinary id (2026-11-18), and a converted person's Buddy must adopt it.
4. A thread like any Chat thread
Decided 2026-11-17: the experience is the same as a T3 Code thread, whether it is open in Buddy's window or in the Chat tab.
BuddyComposerControls(Normal/Fast) is GEN3 only. Upstream's per-thread selection already persists the choice. A new thread takesprojectSettingsOverrides[buddy], else the Environment default. The Platform's recommendation never touches Buddy's project (feat(lazurio): Buddy's project beside the Lazurio Folder, made only by the server and unlisted in Chat #214).buddyProviderTextturns it into the page block for a Buddy-project thread on any provider. The "onlyfast" selection and the instruction stripping stay GEN3-only (Hermes).5. Days
/api/lazurio/buddy/daysresolves Buddy's thread as in step 3 instead of the fixedbuddyid. The grouping (buddyDaysOf) is unchanged.6. Outside this repo (follow-ups, linked when opened)
guest.buddy.generation: 4):T3CODE_LAZURIO_BUDDY_FOLDERandT3CODE_LAZURIO_BUDDY_ORIGINint3code.service, replacing the manual pilot drop-in, not adding to it;buddy.<login>routed tot3code.service;workspace_buddyonly for people not converted;entry.buddy {generation: 4, folder, external_origin}withoutlisten_port.${buddyOrigin}/.lazurio-t3-buddy.service.~/.t3(the shared server) for Buddy's origin.lazurio buddy chat/sign-inare GEN3 only.Open points (for the coordinator)
task-2026-11-16-603), which I run separately on isolated data. If V3 finds that a switch loses too much context, the window can warn on switch. That doesn't change this design.@, "New thread in Buddy", "Initialize Git") get fixed here as they fall in Buddy's window.Plan of work
lazurioBuddyOrigin, project-bound thread and days routes, project-bound prompt pieces, tests.Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread 72068f77-568a-48aa-aa8a-108c03b29972
🤖 Generated with Claude Code