Use imageGenerate for image modification requests

Open Beginner friendly
#119 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
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
ai, documentation

Research direction

Start by locating the tool-usage instructions or skill guidance that describes when to call imageGenerate. Update the guidance for image modification, chart and diagram regeneration, including prompt reconstruction and the limitation that pixel-accurate raster editing is unsupported; done when these cases are clearly covered.

Written by the indexing model from the issue text.

Description

Summary

When a user asks to modify or recreate an image (e.g. update a chart, change a visualization), the assistant currently skips imageGenerate and falls back to non-visual responses. It should recognize these as valid use cases for the image generation tool and attempt to fulfill them visually.

Background

A user requested an image modification (changing a chart). The assistant declined to use imageGenerate even though the task was plausibly in scope. The existing tool-usage guidance says to use imageGenerate when the user wants to visually represent something, but the assistant doesn't connect "modify this image" requests to that definition.

Scope

  • Update tool-usage instructions or skill guidance so the assistant maps image-modification intent (editing, recreating, updating a visual) to imageGenerate calls
  • Likely includes chart regeneration, diagram edits, and similar re-render tasks
  • Out of scope: pixel-level editing of existing rasters (not supported by the underlying tool)

Implementation

  • Clarify in tool-usage docs that "modify an image" and "update this chart/diagram" requests should trigger imageGenerate with a reconstructed prompt
  • Add guidance on how to infer prompt content from the existing image description + requested changes
  • Note limitations (generative output, not pixel-accurate edits)

Action taken on behalf of David Cramer.

Dominant language
TypeScript
Stars
358
Forks
38
Avg merge
7h
Merged PRs (30d)
199

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 getsentry/junior

All issues in getsentry/junior

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.