Skip to content

fix: macOS updater archives, AppImage GST registry, mesh max_tokens#2694

Open
Chessing234 wants to merge 5 commits into
block:mainfrom
Chessing234:fix/updater-console-gst
Open

fix: macOS updater archives, AppImage GST registry, mesh max_tokens#2694
Chessing234 wants to merge 5 commits into
block:mainfrom
Chessing234:fix/updater-console-gst

Conversation

@Chessing234

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • cargo test --features mesh-llm --lib preserves_user_max_output
  • cargo fmt --check, bash -n fix-appimage, YAML parse release.yml
  • release assemble guard (CI)

Made with Cursor

Chessing234 and others added 5 commits July 24, 2026 11:39
Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@bokiko

bokiko commented Jul 24, 2026

Copy link
Copy Markdown

Thanks for the quick fix. I validated the #2558 part of this PR on an independent two-node shared-compute testbed (SmolLM2-135M served over relay-mesh, consumer agent with a per-agent BUZZ_AGENT_MAX_OUTPUT_TOKENS=1024).

Tested at PR head 5c1f22bde279bbdccf86ce55ae84a95bd5e56a91. What I confirmed:

  • The per-agent BUZZ_AGENT_MAX_OUTPUT_TOKENS=1024 now reaches the spawned buzz-acp / buzz-agent (verified on their live process env). Previously the harness always ran 4096 — that clobber is gone.
  • The prior failure is gone: no more 503 … all 0 tunnel(s) from the context fit check. Mesh requests succeed, and a direct completion through the same ingress at max_tokens=1024 returns 200.
  • The added unit test (apply_relay_mesh_env_preserves_user_max_output_tokens) passes.

One caveat so I'm not overstating it: the agent did not post a full channel reply in my run. Inference succeeded (no 503), but SmolLM2-135M didn't produce a postable response — that looks like tiny-model/harness-quality behavior, separate from this PR's fix.

Net: the env-precedence change resolves the clobber and unblocks small-context shared-compute agents at the routing/sizing layer. Happy to run further checks on the testbed if useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants