Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Replay catalog omits the image capacity required by saved histories

Open Beginner friendly
#2,628 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
api, testing

Research direction

Start at the replay proxy's GET /models response and inspect how its fake catalog declares vision limits. Run the named SessionConfigE2ETests and SessionE2ETests attachment and vision scenarios, then confirm the catalog advertises capacity for two images while the saved histories, strict replay matching, and original assertions remain intact.

Written by the indexing model from the issue text.

Description

bug testing

Problem

The replay proxy's GET /models response advertises vision support but does not declare capabilities.limits.vision.max_prompt_images. Saved image conversations can require two image-bearing messages: an attached blob and a subsequent image-view result.

When a runtime applies a one-image fallback for the omitted capability, these histories no longer match the strict replay snapshots. The proxy reports a missing cached response rather than completing the attachment or model-vision scenario.

Affected scenarios include both SessionConfigE2ETests.Should_Accept_Blob_Attachments and SessionE2ETests.Should_Accept_Blob_Attachments, plus SessionConfigE2ETests.Vision_Disabled_Then_Enabled_Via_SetModel.

Expected behavior

The fake catalog should explicitly support the image capacity required by its recorded conversations. Keep the original attachment and vision assertions, saved histories, and strict replay matching intact.

An explicit two-image capacity resolves these scenarios. A harness-only fix and HTTP endpoint regression coverage are prepared; no product change or retry is needed.

Generated by Copilot

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 9h
Merged PRs (30d)
130

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.