github / github/copilot-cli

Support image generation for developer assets (icons, favicons, logos, OG images)

Open
#4,581 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

Describe the feature or problem you'd like to solve

Copilot CLI can read images but cannot produce them. Building any web page, desktop app,
or mobile app needs visual assets that aren't code — app icons at every required size,
favicon.ico, Open Graph preview images, splash screens, placeholder art.

Copilot CLI can scaffold the whole project and write the manifest that references
icon-512.png, but it can't create that file. The developer has to leave the terminal,
generate the asset elsewhere, and come back. That happens on nearly every new project.

To be clear on direction: the deliverable is a file written into the project
directory
, not an image displayed in the terminal.

Why now — billing is usage-based. Since 1 June 2026 Copilot meters usage through AI
Credits (1 credit = $0.01). Image generation is a paid capability and I'd expect to pay
for it per use, charged at its own rate rather than the one designed for text.

Additional context

OpenAI's Codex CLI already ships this as a bundled first-party skill (imagegen) backed
by a built-in image_gen tool, scoped to "website assets, game assets, UI mockups,
product mockups, wireframes, logo design," with a policy that project-bound assets get
written into the workspace rather than left in the tool's default directory.

Also requested for VS Code:
microsoft/vscode#266055.

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.

Research direction

The issue names no implementation files, tests, or entry points; start by locating the CLI's existing image-reading capability and the usage-based billing integration. Define how an image-generation request is invoked, charged, and written into the project directory, then verify that developer assets such as icons, favicons, logos, and OG images are produced at the requested paths.

Written by the indexing model from the issue text.

Assessment

Domain
ai, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.