Skip to content

Reuse cloud skill catalogs across turns until invalidated - #47350

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/ac47d5202d76703c4946afef3b1a48eaf05b54c2
Sep 22, 2026
Merged

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

Conversation

@copyberry

@copyberry copyberry Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Reuse cloud skill catalogs across turns until invalidated

Why

Cloud skill discovery ran on every turn, even when the Apps resource generation and authentication scope were unchanged.

What changed

  • Reuse warning-free catalogs, including empty catalogs, while their authentication scope and Apps resource cache key remain current.
  • Refresh after invalidation and retry failed or partial discovery on the next turn.
  • Reject discovery results if the Apps resource cache key changes during discovery.

Testing

Update lifecycle tests to verify cached turns avoid catalog listings and skill reads, while connection and authentication changes trigger refreshes. Update the referenced-resource test to verify partial discovery retries on the next turn without an explicit MCP refresh.

## Why

Cloud skill discovery ran on every turn, even when the Apps resource generation and authentication scope were unchanged.

## What changed

- Reuse warning-free catalogs, including empty catalogs, while their authentication scope and Apps resource cache key remain current.
- Refresh after invalidation and retry failed or partial discovery on the next turn.
- Reject discovery results if the Apps resource cache key changes during discovery.

## Testing

Update lifecycle tests to verify cached turns avoid catalog listings and skill reads, while connection and authentication changes trigger refreshes. Update the referenced-resource test to verify partial discovery retries on the next turn without an explicit MCP refresh.

GitOrigin-RevId: ac47d5202d76703c4946afef3b1a48eaf05b54c2
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/ac47d5202d76703c4946afef3b1a48eaf05b54c2 branch from 7f0d503 to 8edfca8 Compare September 22, 2026 19:59
@copyberry
copyberry Bot merged commit 8edfca8 into main Sep 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/ac47d5202d76703c4946afef3b1a48eaf05b54c2 branch September 22, 2026 19:59
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 22, 2026
@nitelite
nitelite deployed to issue-triage September 22, 2026 20:03 — with GitHub Actions Active
@nitelite
nitelite deployed to issue-triage September 22, 2026 20:03 — with GitHub Actions Active
@nitelite
nitelite deployed to issue-triage September 22, 2026 20:03 — with GitHub Actions Active
@nitelite
nitelite deployed to issue-triage September 22, 2026 20:04 — with GitHub Actions Active
@Taermoon
Taermoon deployed to issue-triage September 22, 2026 20:07 — with GitHub Actions Active
@Taermoon
Taermoon deployed to issue-triage September 22, 2026 20:07 — with GitHub Actions Active
@Taermoon
Taermoon deployed to issue-triage September 22, 2026 20:07 — with GitHub Actions Active
@rMozes
rMozes deployed to issue-triage September 22, 2026 20:08 — with GitHub Actions Active
@rMozes
rMozes deployed to issue-triage September 22, 2026 20:08 — with GitHub Actions Active
@rMozes
rMozes deployed to issue-triage September 22, 2026 20:08 — with GitHub Actions Active
@rMozes
rMozes deployed to issue-triage September 22, 2026 20:09 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
issue-triage — 8edfca89 Deployed Sep 22, 2026 by rMozes via Identify potential duplicates (open issues fallback) #47497
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.

4 participants