Claude Code and Codex assemble a visual proposal
Suzuki reports using Codex CLI for proposal images and Claude Code to place them in a branded PowerPoint, fixing ambiguous filenames before presenting the completed client proposal.
note.com
Original prompt
Shared by the source author. See source notes for context.
このフォルダの画像を、提案書の表紙と各章扉にそれぞれ配置して、ブランドカラーの枠をつけて、1つのpptxにまとめて
Reach people exploring AI agents
See placements →What happened
Suzuki reports using Codex CLI for proposal images and Claude Code to place them in a branded PowerPoint, fixing ambiguous filenames before presenting the completed client proposal.
Reported by 鈴木章裕How the agent did it
- Define the proposal structure, brand colours and intended audience.
- Use Codex CLI to create cover and chapter-opening images.
- Name each image by its role and place it in the handoff folder.
Where a person stepped in
The author chooses the proposal direction, fixes filename ambiguity and presents the deck. A positive client comment is not evidence of a closed sale or independently measured quality.
鈴木章裕 describes preparing a proposal about adopting generative AI for a prospective client. Claude Code handles the slide structure and writing, but the cover and section-openers need photographic-looking images that his initial workflow does not produce satisfactorily.
He asks Codex CLI for those visuals, then places the image files in a shared folder and hands assembly back to Claude Code. The assistant loads and positions the images, adjusts their sizes, adds brand-coloured framing and exports the PowerPoint. The author says he performs none of the individual pasting himself.
The first handoff is not smooth: inconsistent filenames leave the receiving agent unsure which image belongs on which slide. Naming assets by role, such as cover or chapter-one opener, resolves that ambiguity. The completed proposal is presented to the client, but a favourable comment from the chair does not establish a closed sale or a measured quality gain. The useful artifact contract is the outline plus a role-labelled image folder. The entry credits Claude Code for assembling the file and Codex for generating its image assets, rather than presenting one model as if it performed every stage.
Prompt
Original prompt
Source: Blog · 鈴木章裕
Frequently asked questions
What caused the first handoff problem?
Inconsistent image filenames left Claude Code uncertain about which slide should receive each asset.
How was that corrected?
The author named images by role, such as cover and chapter opener, before handing the folder to the assembly agent.
Did the proposal win a contract?
The source reports a favourable client comment at presentation, not a signed contract or measured sales result.
More details
Remaining steps
- Have Claude Code position the images and export the PowerPoint.
- Inspect and present the completed proposal as the human author.
About this account
Codex generates visual assets; Claude Code reads the role-labelled files and automates image placement, sizing and PowerPoint assembly under the author’s direction.
Firsthand account by 鈴木章裕; original publication date verified against Primary Japanese note 2026年7月8日 07:42. Outcomes are the author’s reports, not independently reproduced. Original Japanese assembly instruction shared by the author; Codex generated the images used in this Claude Code stage.
Credit: 鈴木章裕
Source published 8 Jul 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Codex CLI · Image folder · PowerPoint · Brand colours
Proposal image handoff · Role-labelled assets · Slide assembly
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.