Skip to content

fix: active community rail, Codex nest isolation, ecosystem docs#2710

Open
Chessing234 wants to merge 3 commits into
block:mainfrom
Chessing234:fix/community-codex-docs
Open

fix: active community rail, Codex nest isolation, ecosystem docs#2710
Chessing234 wants to merge 3 commits into
block:mainfrom
Chessing234:fix/community-codex-docs

Conversation

@Chessing234

Copy link
Copy Markdown
Contributor

Summary

  • Active community shows a rail pill + ring even with custom icons
  • Managed Codex agents use CODEX_HOME=~/.buzz/.codex (auth handed off)
  • Ecosystem docs point at buzz-releases and note legacy sprout-* names

Test plan

  • just ci
  • Join 2+ communities with custom icons → active one is obvious in the rail
  • Start a Codex agent → sessions land under ~/.buzz/.codex, not personal Codex Remote
  • Skim AGENTS.md ecosystem table for the rename note

Closes #2570
Closes #2660
Closes #2557

Made with Cursor

Chessing234 and others added 3 commits July 24, 2026 14:09
Add a Discord-style pill and ring so the selected community stays
visible even when a custom icon covers the tile fill.

Closes block#2570

Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Set CODEX_HOME to ~/.buzz/.codex and hand off auth.json so Buzz-managed
sessions stop appearing in the user's Codex / Remote history.

Closes block#2660

Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Match README/RELEASING for the signed-desktop GitHub repo and note which
private pipelines still keep legacy sprout-* names.

Closes block#2557

Signed-off-by: Taksh <takshkothari09@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant