Skip to content

Add explicit local board connections with fixed runtime access - #53400

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/f92410c3a5c6a46920c3e0e71849c85dc83d9c31
Oct 12, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/f92410c3a5c6a46920c3e0e71849c85dc83d9c31

Conversation

@copyberry

@copyberry copyberry Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

Add explicit local board connections with fixed runtime access

Why

Local message boards were scoped to an agent tree. Independently created Codex runtimes need a way to share a board while receiving different access permissions.

What changed

  • Add LocalBoard and LocalBoardConnection so hosts can supply read-only or read-write access through thread_extension_init, including for isolated, ephemeral runtimes.
  • Allow read-only connections to read and manage their own subscriptions; reject posting, replying, channel creation, and changes to another agent's subscriptions. Expose effective permissions in channel discovery.
  • Use unique runtime paths and require matching board IDs and canonical database paths when resolving agents or delivering notifications.
  • Document explicit extension installation and connection setup for new runtimes, cold resumes, and forks.

Testing

Add a scenario and context snapshot covering an independent writer and isolated Guardian sharing a board through a symlink alias, read-only permission denials, subscription and explicit notifications, and rejection of notifications to an unconnected runtime before a post is written.

## Why

Local message boards were scoped to an agent tree. Independently created Codex runtimes need a way to share a board while receiving different access permissions.

## What changed

- Add `LocalBoard` and `LocalBoardConnection` so hosts can supply read-only or read-write access through `thread_extension_init`, including for isolated, ephemeral runtimes.
- Allow read-only connections to read and manage their own subscriptions; reject posting, replying, channel creation, and changes to another agent's subscriptions. Expose effective permissions in channel discovery.
- Use unique runtime paths and require matching board IDs and canonical database paths when resolving agents or delivering notifications.
- Document explicit extension installation and connection setup for new runtimes, cold resumes, and forks.

## Testing

Add a scenario and context snapshot covering an independent writer and isolated Guardian sharing a board through a symlink alias, read-only permission denials, subscription and explicit notifications, and rejection of notifications to an unconnected runtime before a post is written.

GitOrigin-RevId: f92410c3a5c6a46920c3e0e71849c85dc83d9c31
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/f92410c3a5c6a46920c3e0e71849c85dc83d9c31 branch from b0661bc to 97239fd Compare October 12, 2026 14:44
@copyberry
copyberry Bot merged commit 97239fd into main Oct 12, 2026
1 check passed
@chatgpt-codex-connector

Copy link
Copy Markdown
Contributor

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-12T14:44:37.700558Z b0661bc PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/f92410c3a5c6a46920c3e0e71849c85dc83d9c31 branch October 12, 2026 14:44
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 12, 2026
@odcpw
odcpw deployed to issue-triage October 12, 2026 14:46 — with Image GitHub Actions Active
@odcpw
odcpw deployed to issue-triage October 12, 2026 14:46 — with Image GitHub Actions Active
@odcpw
odcpw deployed to issue-triage October 12, 2026 14:46 — with Image GitHub Actions Active
@odcpw
odcpw deployed to issue-triage October 12, 2026 14:47 — with Image GitHub Actions Active
@derspotter
derspotter deployed to issue-triage October 12, 2026 14:51 — with Image GitHub Actions Active
@derspotter
derspotter deployed to issue-triage October 12, 2026 14:51 — with Image GitHub Actions Active
@derspotter
derspotter deployed to issue-triage October 12, 2026 14:51 — with Image GitHub Actions Active
@derspotter
derspotter deployed to issue-triage October 12, 2026 14:52 — with Image GitHub Actions Active
@TechGenDM
TechGenDM deployed to issue-triage October 12, 2026 14:53 — with Image GitHub Actions Active
@TechGenDM
TechGenDM deployed to issue-triage October 12, 2026 14:53 — with Image GitHub Actions Active
@TechGenDM
TechGenDM deployed to issue-triage October 12, 2026 14:53 — with Image GitHub Actions Active
@makeitrad
makeitrad deployed to issue-triage October 12, 2026 14:58 — with Image GitHub Actions Active
@makeitrad
makeitrad deployed to issue-triage October 12, 2026 14:58 — with Image GitHub Actions Active
@makeitrad
makeitrad deployed to issue-triage October 12, 2026 14:58 — with Image GitHub Actions Active
@Eki-Raku
Eki-Raku deployed to issue-triage October 12, 2026 15:10 — with Image GitHub Actions Active
@Eki-Raku
Eki-Raku deployed to issue-triage October 12, 2026 15:10 — with Image GitHub Actions Active
@Eki-Raku
Eki-Raku deployed to issue-triage October 12, 2026 15:10 — with Image GitHub Actions Active
@Eki-Raku
Eki-Raku deployed to issue-triage October 12, 2026 15:11 — with Image GitHub Actions Active
@s9008129
s9008129 deployed to issue-triage October 12, 2026 15:13 — with Image GitHub Actions Active
@s9008129
s9008129 deployed to issue-triage October 12, 2026 15:13 — with Image GitHub Actions Active
@s9008129
s9008129 deployed to issue-triage October 12, 2026 15:13 — with Image GitHub Actions Active

This branch was successfully deployed

1 active deployment
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.