Skip to content

feat(mesh): upgrade to mesh-llm 0.76.0-rc8 and recommend Qwen3.8 27B - #6189

Merged
michaelneale merged 35 commits into
mainfrom
micspiral/mesh-0.76.0-rc3
Sep 8, 2026
Merged

feat(mesh): upgrade to mesh-llm 0.76.0-rc8 and recommend Qwen3.8 27B#6189
michaelneale merged 35 commits into
mainfrom
micspiral/mesh-0.76.0-rc3

Conversation

@micspiral

@micspiral micspiral commented Aug 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Upgrades Buzz's mesh-llm dependencies through the released v0.76.0-rc8 tag (2040765d), including the Qwen3.8 curated recommendation and rc8's scheduler/runtime improvements.

fixes: #6724

This PR also:

  • seeds BUZZ_AGENT_LLM_TIMEOUT_SECS=660 for mesh agents, above MeshLLM's 600-second backend timeout;
  • recommends Qwen3.8 27B Q4_K_M for 64 GB-and-larger machines, then ladders down through Gemma 4 E4B and Qwen 9B for smaller machines;
  • keeps stored shared-compute auto translated to MeshLLM's supported wire model mesh.

@micspiral
micspiral requested a review from a team as a code owner August 18, 2026 02:26
@michaelneale
feat(mesh): upgrade to mesh-llm 0.76.0-rc3 and recommend Qwen3.8 27B
96e0c7f 
Bump every mesh-llm git dependency in buzz-relay and buzz-desktop from
v0.75.1 to v0.76.0-rc3, and make Qwen3.8 27B Q4_K_M the curated pick for
64GB-class machines.

The rc carries the two changes that make Qwen3.8 safe to recommend:
Mesh-LLM/mesh-llm#1283 routes Qwen3.8 identities to the qwen35 recurrent
family (without it the identity compacts to a string matching neither
qwen35 nor qwen36, so a hybrid recurrent model is classified as dense
attention-KV), and #1342 restores recurrent shared prefixes. #1343 adds
Qwen3.8-27B-Q4_K_M to the compiled MODEL_CATALOG.

Because the large pick now exists in MODEL_CATALOG, the synthesized
catalog entry Buzz carried for the gemma-4-26B pick is removed along with
its size/file/description constants; the entry is canonicalized from the
upstream catalog instead. The retired gemma-4-26B alias is kept in
canonical_curated_model_id so machines that already selected it keep
resolving to a model id Mesh's OpenAI ingress accepts.

Dependency resolution notes: iroh moves 1.0.2 -> 1.0.3 to match the rc's
requirement, and libsqlite3-sys moves 0.30.1 -> 0.35.0 because the rc's
mesh-llm-log-store requires rusqlite 0.37 (only one package may link
sqlite3).

Verification: cargo check passes for buzz-relay and for buzz-desktop with
--features mesh-llm; 2611 buzz-desktop tests pass; cargo fmt --check is
clean. Two failures predate this change and reproduce on unmodified
origin/main: the global_config
inherited_shared_compute_translates_to_supported_agent_transport
assertion (expects "auto", gets "mesh") and an items-after-test-module
clippy lint in managed_agents/restore.rs. Not runtime-verified against a
live Qwen3.8 mesh node from this branch.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
@michaelneale
fix(desktop): stop abandoning healthy mesh prefills at four minutes
0eecc0c 
buzz-agent's `BUZZ_AGENT_LLM_TIMEOUT_SECS` defaults to 240s. MeshLLM's
OpenAI frontend gives a backend call 600s
(`OpenAiFrontendConfig::DEFAULT_BACKEND_TIMEOUT`), so on shared compute the
client aborts work the server is still legitimately doing.

Requests to a local mesh are `stream: false`, so a cold multi-ten-thousand
token prefill is one silent request. Measured on an M5 Max serving
Qwen3.8-27B Q4_K_M: an 88,318-token cold prompt returns HTTP 200 after
503s at 176 tok/s prefill. At the 240s default the client gives up at
four minutes, then retries with an escalated budget (240 -> 480 -> 960),
piling load onto a box that is already prefilling the first attempt.

Seat the mesh client budget at 660s, just above the frontend's 600s, so
the mesh's own error surfaces rather than a client abort racing it.
Remote providers are untouched and keep buzz-agent's 240s default. Like
the other mesh seeds this is a default, not policy: an explicit user
value survives via `insert_default_if_unset` plus the copy-forward list
in `relay_mesh_process_env`.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
@michaelneale
feat(mesh): move mesh-llm dependency to 0.76.0-rc4
0cd224c 
Bump every mesh-llm git dependency in buzz-relay and buzz-desktop from
the v0.76.0-rc3 tag to v0.76.0-rc4.

rc4 is a low-risk move from rc3: git diff v0.76.0-rc3..v0.76.0-rc4 in
Mesh-LLM/mesh-llm touches only generated console web assets and the
release version bump, so the runtime behaviour Buzz depends on is the
same code we already validated. It is the first release tag carrying the
Qwen3.8 fixes as a downloadable artifact for every platform, which means
nodes no longer need a source build to serve the curated large pick.

The Qwen3.8 27B curated recommendation from the rc3 commit is unchanged.

Verification: cargo check passes for buzz-relay and for buzz-desktop
with --features mesh-llm. The one warning emitted (unreachable statement
in commands/workspace.rs) predates this change.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
@micspiral
micspiral force-pushed the micspiral/mesh-0.76.0-rc3 branch from 777426b to 0cd224c Compare August 20, 2026 02:08
@micspiral micspiral changed the title feat(mesh): upgrade to mesh-llm 0.76.0-rc3 and recommend Qwen3.8 27B feat(mesh): upgrade to mesh-llm 0.76.0-rc4 and recommend Qwen3.8 27B Aug 20, 2026
@michaelneale
fix(dev): honor mesh=1 in desktop-standalone
92ecac2 
desktop-standalone was the only launch recipe that ignored the `mesh`
variable. dev, staging and production all build FEATURES=(--features
mesh-llm) when it is set; desktop-standalone invoked `tauri dev` with no
features, so `just mesh=1 desktop-standalone` silently produced a
non-mesh build and the app reported "mesh-llm feature not enabled" from
desktop/src-tauri/src/mesh_llm_stubs.rs.

Wire it up the same way as the other three recipes.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
@micspiral
micspiral marked this pull request as draft August 20, 2026 08:59
Jimmy @michaelneale
feat(mesh): move mesh-llm dependency to 0.76.0-rc6
a6b4756 
Bump every mesh-llm git dependency in buzz-relay and buzz-desktop from
the v0.76.0-rc4 tag to v0.76.0-rc6, and regenerate both lockfiles at
tag commit a8ddb455.

Verification: cargo check -p buzz-relay --all-targets and cargo check
--manifest-path desktop/src-tauri/Cargo.toml --features mesh-llm
--all-targets pass. The desktop check retains the pre-existing
unreachable-code warning in commands/workspace.rs. The buzz-relay package
suite compiled rc6 and ran 892 passing tests, but its existing mesh demo
forwarded-arm test timed out with HTTP 504 twice.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
@micspiral micspiral changed the title feat(mesh): upgrade to mesh-llm 0.76.0-rc4 and recommend Qwen3.8 27B feat(mesh): upgrade to mesh-llm 0.76.0-rc6 and recommend Qwen3.8 27B Aug 21, 2026
michaelneale and others added 4 commits August 25, 2026 11:17
@michaelneale
fix(mesh): run the mesh unenforced on relays that do not enforce memb…
d99cba5 
…ership

Mesh admission is seeded from the relay's NIP-43 membership snapshot
(kind:13534), which is built purely from the `relay_members` table. On a
relay running with `BUZZ_REQUIRE_RELAY_MEMBERSHIP=false`, signing in never
writes a `relay_members` row, so that snapshot lists at most whoever was
added out of band. Ordinary participants are absent from it.

Desktop treated that as an authoritative roster, so every node resolved an
empty intersection, fell back to `trust_owners([self])`, and sat at "1 NODE"
with an empty peer list forever. Two machines sharing compute on the same
open relay could never see each other, through any number of restarts.

Admission was only part of it: `availability_from_events` also required a
snapshot and filtered status notes to `members.contains(reporter)`, so
serve-target discovery was membership-gated too. Relaxing admission alone
would still have left peers undiscoverable.

Resolve the relay's membership mode from its NIP-11 document instead. The
relay advertises NIP-43 only when membership is actually enforced, so the
advertisement is a faithful signal. When it is absent, skip the snapshot
requirement for routing and pass `trusted_owner_ids: None`, which the
existing SDK path already maps to `TrustPolicy::Off` — stock MeshLLM
behaviour, scoped by the relay-derived mesh topic.

Membership emptiness deliberately does NOT drive this. On an enforcing relay
a missing snapshot is a transient replication gap, and the existing code
treats it as an error precisely so a blip cannot flap a live node down to
self-only. Keying open-mesh off "no snapshot" would have turned that blip
into a silent loss of admission enforcement. A failed NIP-11 probe therefore
falls back to the enforcing behaviour: an unreachable relay can never relax
admission.

Closed-relay behaviour is unchanged, including the fail-closed error and the
shrink hysteresis. `roster_reconcile_action` maps `Ok(None)` to `Keep`: a
node already enforcing an allowlist keeps it, so a mid-flight NIP-11 change
cannot de-restrict a running mesh.

Freshness and owner-signed endpoint binding still gate routing on an open
relay; only the membership intersection is lifted.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
@michaelneale
Merge remote-tracking branch 'origin/main' into micspiral/mesh-0.76.0…
8cffb88 
…-rc3

* origin/main: (86 commits)
  Centralize replaceable event persistence (#6660)
  feat(workflows): discover trigger filter values (#6712)
  feat(desktop): simplify the message action rail (#6529)
  fix(desktop): restore icon-only remote marker (#6491)
  fix(ci): prevent poisoned Rust caches (#6618)
  docs(security): route reports through private advisories (#6728)
  fix(composer): wrap Buzz chip labels without orphaning icons (#6581)
  fix(desktop): bound thread /query and surface load errors, not false-empty (#6447)
  fix(messages): route edits to the owning composer (#6575)
  fix(mobile): join starter channels after accepting invite (#5915)
  Add mobile profile editing (#6583)
  fix(desktop): align jump-to-latest pill with composer height (#6606)
  fix(desktop): emit singular `mention` feed category so alerts route correctly (#6665)
  fix(mobile): recover stale and shuffled messages (#6691)
  feat(mobile): browse and join open channels (#6243)
  show mention counts in channel notifications (#6696)
  fix(desktop): hide selection formatting tray on composer right-click (#6683)
  fix(desktop): stabilize members dialog scrolling (#6670)
  fix(desktop): keep member runtime status off the UI thread (#6445)
  perf(desktop): persist channel heads, collapse thread reads and reply sends (#6572)
  ...
@michaelneale
fix(mesh): make open-relay mode consistent across discovery, reconcil…
ceaaced 
…e, and probing

Follow-up to the open-mesh change (d99cba5), closing three gaps found in
review:

1. A stray membership snapshot on an open relay no longer gates routing.
   Admission runs TrustPolicy::Off there, but discovery still intersected
   status notes with any kind:13534 roster that happened to exist (added out
   of band), and the query layer applied the same authors filter — a hybrid
   where admission admits everyone while discovery hides non-roster peers.
   Both branches now check the relay mode: open relays ignore membership
   entirely and rely on freshness plus owner-signed endpoint binding.

2. Reconcile recovers a node isolated by the startup probe fallback. A
   transient NIP-11 probe failure at start falls back to the enforcing path
   and a self-only allowlist; treating Ok(None) as an unconditional Keep then
   pinned that node at "1 NODE" until an app restart — the original bug,
   reintroduced by one HTTP blip. A self-only roster admits nobody else, so
   restarting into open mesh relaxes nothing that protected anyone. An
   allowlist admitting other owners is still never relaxed mid-flight.

3. Successful NIP-11 probes are memoized per relay URL. The deployment mode
   does not flap at runtime, and discovery re-probed on every reconcile poll.
   Failures are not cached, so the fallback in (2) re-probes and recovers.

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
Jimmy
feat(mesh): move mesh-llm dependency to 0.76.0-rc7
fa252b5 
Bump every MeshLLM git dependency in buzz-relay and buzz-desktop from v0.76.0-rc6 to the released v0.76.0-rc7 tag at 5d07a20b, and regenerate both lockfiles. The transitive lockfile delta follows rc7's dependency graph; json5 is removed and the Windows/proc-macro families move to the versions rc7 selects.

Review also closes two open-relay gaps: malformed NIP-11 mode evidence now keeps the fail-closed fallback, and persisted-agent bootstrap target resolution uses the relay mode instead of reapplying closed-membership filtering on open relays.

Verification: both package suites compile against rc7. Desktop mesh-focused tests pass (88 passed, 1 ignored). The full desktop suite retains the pre-existing inherited shared-compute assertion failure (mesh vs auto); the relay suite retains the pre-existing mesh demo forwarded-arm HTTP 504 (908 passed, 1 failed, 48 ignored).

Co-authored-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
@micspiral micspiral changed the title feat(mesh): upgrade to mesh-llm 0.76.0-rc6 and recommend Qwen3.8 27B feat(mesh): upgrade to mesh-llm 0.76.0-rc7 and recommend Qwen3.8 27B Aug 25, 2026
Jimmy and others added 5 commits August 25, 2026 15:04
Jimmy
fix(mesh): restore hardware model ladder
49efb1c 
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Co-authored-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Jimmy
Merge origin/main into mesh rc7 upgrade
78e3e16 
Co-authored-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
@michaelneale
Merge commit '78e3e1684ba688bd851114785d3a36a58588e8cb' into local/pr…
abc594c 
…-6189-fresh

Co-authored-by: Michael Neale <michael.neale@gmail.com>
Signed-off-by: Michael Neale <michael.neale@gmail.com>
Jimmy @micspiral
fix(mesh): classify relay mode in model discovery
109e553 
Route agent-form shared-compute discovery through the same NIP-11 mode resolution used by mesh startup and routing. Open relays no longer trigger the closed-relay member-roster warning.

Co-authored-by: Mic Neale <305999590+micspiral@users.noreply.github.com>
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Jimmy
Merge remote-tracking branch 'origin/main' into local/pr-6189-fresh
cbba755 
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
@micspiral
micspiral marked this pull request as ready for review August 26, 2026 07:11
wesbillman
wesbillman requested changes Aug 27, 2026
View reviewed changes

@wesbillman wesbillman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Requesting changes at cbba75536e9226c760e49cb75281a3e79d20783c for two admission-contract gaps: a running open mesh never tightens after the relay begins enforcing membership, and malformed supported_nips elements can fail open. All reported CI checks are green at this head, but they do not cover these authority transitions and malformed-input boundaries.

Comment thread desktop/src-tauri/src/commands/mesh_llm.rs Outdated
Comment thread desktop/src-tauri/src/mesh_llm/discovery.rs Outdated
Jimmy added 4 commits August 27, 2026 11:45
Jimmy
fix(mesh): refresh relay admission mode safely
96dd6a9 
Reject partially malformed supported_nips arrays instead of treating an ambiguous NIP-11 document as evidence that membership is disabled. Remove the permanent relay-mode cache so open runtimes can detect a relay that later enables membership enforcement.

Keep established closed runtimes on their existing roster-only reconcile path. Only open and startup-fallback self-only runtimes re-probe mode; failed probes preserve the current policy, while a valid closed result restarts into the fetched allowlist.

Co-authored-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Jimmy
Merge remote-tracking branch 'origin/main' into local/pr-6189-fresh
1eba2f0 
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Jimmy
fix(mesh): keep closed availability helper test-only
3e78b29 
The mode-aware resolver replaced the legacy closed-only helper in production. Keep the compatibility wrapper available to its existing closed-mode tests without leaving an unused production export.

Co-authored-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Jimmy
test(mesh): prove relay mode probes are refreshed
34e31f7 
Exercise the real NIP-11 HTTP probe three times at one URL as its response changes from open to closed to malformed. This guards against restoring the permanent mode cache and proves malformed evidence cannot be interpreted as open.

Co-authored-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
Signed-off-by: Jimmy <1fe240cd1a8cf775f6f3060f115e5a303181f3abf28ad4cb0c2515f4a02b36a8@meshllm.communities.buzz.xyz>
@micspiral
micspiral requested a review from wesbillman August 27, 2026 05:00
@michaelneale

michaelneale commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

thanks @wesbillman, addressed

@micspiral
micspiral enabled auto-merge (squash) August 27, 2026 05:25
michaelneale added a commit to Mesh-LLM/mesh-llm that referenced this pull request Aug 27, 2026
@michaelneale
test(moa): pin committee shape on the Buzz curated ladder
c0f9cf2 
The MoA fleet sim used a synthetic tier mix. Buzz's shipped picker
(block/buzz#6189, desktop/src-tauri/src/mesh_llm/catalog.rs) recommends
exactly one model per rated-memory class, so a real fleet only ever
advertises three names — and two of them are below SMALL_TIER_MAX_B.

Pin what the shipped assembly path does on that ladder:

  laptops only (E4B x50)         50 nodes ->  1 worker
  mid only (9B x50)              50       ->  1
  laptops + mid                 100       ->  1
  one big (27B x1)                1       ->  1
  two big (27B x2)                2       ->  2
  big fleet (27B x100)          100       ->  2
  full ladder, one big          101       ->  3
  full ladder, many big         900       ->  3

Two claims are asserted rather than printed:

  * An all-laptop Buzz fleet never convenes a committee. Every rung
    below 80 GB is small-tier (Qwen3.5-9B misses the 10.0 boundary by
    1B), and an all-small pool collapses to its best member — the
    measured small-width regression in evals/moa-openrouter/RESULTS.md.
  * Two 80GB+ machines on the same 27B is the only shape on this ladder
    that reaches a real committee, via same-model self-fill. It is the
    homogeneous case the mid-scale eval measured at 48W/23T/2L, and
    RefinementPolicy::Auto enables the refine round for it.

No production behaviour changes.

Co-authored-by: Michael Neale <14976+michaelneale@users.noreply.github.com>
Signed-off-by: Michael Neale <14976+michaelneale@users.noreply.github.com>
wpfleger96 pushed a commit that referenced this pull request Sep 8, 2026
Hayt
Merge remote-tracking branch 'origin/main' into hayt/nip-fi-stateless…
a9e091a 
…-enforcement

* origin/main:
  feat(mesh): upgrade to mesh-llm 0.76.0-rc8 and recommend Qwen3.8 27B (#6189)
  fix(agent): route GPT-5+ model-service FQNs to Responses (#7358)
  fix(buzz-acp): wake held ACP threads and fence forked sessions (#7340)
  fix(mobile): style inline code with the app mono face (#6631)
  chore(release): release Buzz Desktop version 0.5.23 (#7381)
  fix(desktop): keep packaged frontendDist relative so Windows embeds assets (#7177)
  fix(sidebar): simplify unread indicators and emphasize priority activity (#7134)

Signed-off-by: Hayt <9e1c23a3fd83f61da34420e4e88ff1b16e45cafcc0cd9019eb07d4ecfa8ca9b0@buzz.block.builderlab.xyz>
morgmart added a commit that referenced this pull request Sep 8, 2026
@morgmart
Merge remote-tracking branch 'origin/main' into desktop-new
f4afd71 
* origin/main:
  feat(mesh): upgrade to mesh-llm 0.76.0-rc8 and recommend Qwen3.8 27B (#6189)
  fix(agent): route GPT-5+ model-service FQNs to Responses (#7358)
  fix(buzz-acp): wake held ACP threads and fence forked sessions (#7340)
  fix(mobile): style inline code with the app mono face (#6631)
  chore(release): release Buzz Desktop version 0.5.23 (#7381)
  fix(desktop): keep packaged frontendDist relative so Windows embeds assets (#7177)
  fix(sidebar): simplify unread indicators and emphasize priority activity (#7134)

Signed-off-by: morgmart <98432065+morgmart@users.noreply.github.com>
brow added a commit that referenced this pull request Sep 8, 2026
@brow
Merge main to satisfy the pre-push branch-skew gate
581fd52 
* origin/main: (29 commits)
  fix(acp): pace targeted overflow recovery on consumer capacity (#7325)
  fix(link-preview): keep composer fetches user-paced (#7211)
  feat(mesh): upgrade to mesh-llm 0.76.0-rc8 and recommend Qwen3.8 27B (#6189)
  fix(agent): route GPT-5+ model-service FQNs to Responses (#7358)
  fix(buzz-acp): wake held ACP threads and fence forked sessions (#7340)
  fix(mobile): style inline code with the app mono face (#6631)
  chore(release): release Buzz Desktop version 0.5.23 (#7381)
  fix(desktop): keep packaged frontendDist relative so Windows embeds assets (#7177)
  fix(sidebar): simplify unread indicators and emphasize priority activity (#7134)
  Add generic information-flow control core (#7293)
  feat(buzz-acp): update base prompt; add buzz context and skills to Pi agents (#7335)
  fix(desktop): restore mention chip identity icons (#7338)
  Persist video playback speed preference (#7336)
  Verify ACP relay events before prompt routing (#7010)
  fix(buzz-acp): bound busy-owner hold to prevent cross-channel starvation (#7337)
  feat(desktop): invite owned agents from standalone forums (#7125)
  fix(desktop): authorize remote mentions at publication (#7124)
  fix(acp): rename system tag to agent-instructions (#7332)
  fix(desktop): bind duplicate mention selections to exact recipients (#7133)
  refactor(relay): extract NIP-29 membership authorization (#7285)
  ...

Signed-off-by: Tom Brow <tomb@block.xyz>
@Theremoteaidoc Theremoteaidoc mentioned this pull request Sep 8, 2026
Merged
Theremoteaidoc added a commit to Theremoteaidoc/buzz that referenced this pull request Sep 8, 2026
@Theremoteaidoc
Resolve dependency advisories and fork registry routing
bcf7497 
Adapt MeshLLM migration from block/buzz block#6189 and model translation from block#5289. Update h2 and webbrowser in both dependency graphs, exercise mesh-enabled desktop tests, and use configured fork namespaces for Docker caches and provenance.

Signed-off-by: orchestrator <neo870123@gmail.com>
jrobotham-square added a commit to jrobotham-square/buzz that referenced this pull request Sep 8, 2026
@jrobotham-square
Merge remote-tracking branch 'origin/main' into jrobotham/provider-cu…
1c189ae 
…stody

* origin/main:
  fix(acp): pace targeted overflow recovery on consumer capacity (block#7325)
  fix(link-preview): keep composer fetches user-paced (block#7211)
  feat(mesh): upgrade to mesh-llm 0.76.0-rc8 and recommend Qwen3.8 27B (block#6189)
  fix(agent): route GPT-5+ model-service FQNs to Responses (block#7358)
  fix(buzz-acp): wake held ACP threads and fence forked sessions (block#7340)
  fix(mobile): style inline code with the app mono face (block#6631)

Signed-off-by: Joel Robotham <jrobotham@squareup.com>
rileycrane pushed a commit that referenced this pull request Sep 8, 2026
Sol
Merge remote-tracking branch 'origin/main' into fizz/md-viewer
8120875 
* origin/main: (77 commits)
  fix(acp): pace targeted overflow recovery on consumer capacity (#7325)
  fix(link-preview): keep composer fetches user-paced (#7211)
  feat(mesh): upgrade to mesh-llm 0.76.0-rc8 and recommend Qwen3.8 27B (#6189)
  fix(agent): route GPT-5+ model-service FQNs to Responses (#7358)
  fix(buzz-acp): wake held ACP threads and fence forked sessions (#7340)
  fix(mobile): style inline code with the app mono face (#6631)
  chore(release): release Buzz Desktop version 0.5.23 (#7381)
  fix(desktop): keep packaged frontendDist relative so Windows embeds assets (#7177)
  fix(sidebar): simplify unread indicators and emphasize priority activity (#7134)
  Add generic information-flow control core (#7293)
  feat(buzz-acp): update base prompt; add buzz context and skills to Pi agents (#7335)
  fix(desktop): restore mention chip identity icons (#7338)
  Persist video playback speed preference (#7336)
  Verify ACP relay events before prompt routing (#7010)
  fix(buzz-acp): bound busy-owner hold to prevent cross-channel starvation (#7337)
  feat(desktop): invite owned agents from standalone forums (#7125)
  fix(desktop): authorize remote mentions at publication (#7124)
  fix(acp): rename system tag to agent-instructions (#7332)
  fix(desktop): bind duplicate mention selections to exact recipients (#7133)
  refactor(relay): extract NIP-29 membership authorization (#7285)
  ...

Signed-off-by: Sol <478bb5a31222ea2b28a3d1afb8b1d598940628f19c2a87efc3c4b822299eeec6@buzz.block.builderlab.xyz>

# Conflicts:
#	desktop/src-tauri/src/commands/media_download.rs
#	desktop/src-tauri/src/lib.rs
This was referenced Sep 9, 2026
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
@mfethe1 mfethe1 mentioned this pull request Sep 9, 2026
Open
@micspiral micspiral mentioned this pull request Sep 10, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@michaelneale michaelneale michaelneale left review comments
@wesbillman wesbillman wesbillman approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Shared-compute node silently dropped when home relay not in MESH_LLM_DEFAULT_RELAYS

4 participants

@micspiral @michaelneale @wesbillman @sandro-sq