# Can Codex build developer cheat-sheet pins whose examples have actually been run? > Source: https://tareno.co/agents/codex/pinterest > Language: en > Last reviewed: 2026-10-24 > Use Codex with Tareno to turn documentation into a tall cheat-sheet image whose examples were run, write the Pinterest title and description and save a draft you approve in Tareno. ## Connection facts | Field | Value | | --- | --- | | Product surface | Codex (codex) | | Available connection | Published plugin | | Connection evidence | documented | | Methods | plugin, mcp | | Authentication | oauth | | Setup | [Setup guide](https://tareno.co/docs/mcp/openai) | | Install or connect | [Open setup](https://chatgpt.com/plugins/plugin_asdk_app_6a54fa8fd95c81918e64891984183432) | | Evidence observed | 2026-10-27 | | Facts reviewed | 2026-10-27 | Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface. Agent: Codex · Network: Pinterest · Hub: [Codex and Tareno](https://tareno.co/agents/codex) ## Short answer **Can Codex create a cheat-sheet pin for developers and save it through Tareno?** Partly. Codex reads the documentation, runs the examples, generates a tall cheat-sheet image from them and writes the pin text. You upload the image to your Tareno library, and Codex saves the draft with the board. It cannot judge whether the image reads well at feed size, and scheduling needs your approval in Tareno. Developers save cheat sheets: a page of git commands, a regular-expression summary, a table of status codes. Pinterest is an odd but real home for them, because the platform rewards tall, useful images that people keep. The risk is a cheat sheet with a wrong example, which gets saved and trusted. Codex can read the documentation, run each example and build the image from output it has seen. This page follows the author of a small tooling blog through a cheat-sheet pin, with the run-it-first rule, the 2:3 shape and a candid note about what Codex cannot do: look at the result as a reader would. ## Example: a tooling blogger pins a git cheat sheet Imagine a blogger who wants a one-page git cheat sheet for her blog. She asks Codex to take twelve commands from her own tutorial, run each in a scratch repository and keep only those whose output matches the tutorial. Two differ, because the default branch name changed in the git version she runs. Codex fixes the text, generates a tall 1000 by 1500 pixel PNG from an HTML template and writes the title and description of the pin. She looks at the image at thumbnail size, finds the font too small, and asks for a change. She uploads the final file and Codex saves the draft with `create_drafts`. ## Step by step 1. **Pick the commands from your own material.** Point Codex at the tutorial or documentation page. A cheat sheet is only as good as its source, and your own tested text is better than a remembered summary. 2. **Run every example.** Ask Codex to run each command in a scratch environment and compare the output with the text. Examples that differ are fixed or removed, and the git version is noted on the sheet. 3. **Generate the tall image.** Ask for a 1000 by 1500 pixel PNG, the 2:3 shape that Tareno's configuration recommends for Pinterest. Codex can build it from an HTML or SVG template and export it. 4. **Check it at feed size.** Open the image at thumbnail size yourself. Codex cannot see how it reads in a feed, so a font that is fine on a monitor but too small on a phone is a problem you notice, not Codex. 5. **Upload and save the draft.** Upload the final file to the Tareno library. Codex finds it with `list_media`, lists boards with `get_platform_options` and saves the pin through `create_drafts` with the tutorial URL as the link. 6. **Request a time and approve.** Give a day, a time and an IANA time zone. The request becomes a pending action, and you approve it in the Tareno dashboard before Pinterest receives anything. ## Prompts to copy ### Pick and run the commands ```text As material for a Tareno pin, choose from my tutorial [file or URL] the twelve git commands most useful to beginners, run each one in a scratch repository and show me the output next to the output my tutorial claims. Tell me the git version and list every command whose output differs. ``` ### Build the image ```text Build a 1000 by 1500 pixel PNG cheat sheet from the verified commands, with a large title, two columns and a font that stays readable when the image is shown at 200 pixels wide. Add the git version in the footer, and give me the file path. ``` ### Write the pin text ```text Write the Pinterest title within 100 characters and a description of about 300 characters for the cheat sheet, naming the git version and the number of commands. Add one sentence of alt text that lists the sections of the sheet for someone who cannot see it. ``` ### Save to Tareno ```text Use Tareno to find the file [git-cheatsheet.png] in my media library, list my Pinterest boards and save the approved pin as a draft with the tutorial URL as the link and the board I confirm. Return the draft ID, and request no time yet. ``` ## Pinterest in Tareno - Tareno's configuration for Pinterest requires media and recommends a 2:3 image, jpg or png, which suits a tall cheat sheet. - Pinterest's API description allows alt text of up to 500 characters, enough to list the sections of a cheat sheet for a reader who cannot see it. - Tareno's configuration puts the destination link in its own field without an automatic preview, so the tutorial URL is a field of the pin. - Tareno has no tool that creates a board, so a board for developer references has to exist on Pinterest first. Official rules ([Pinterest API v5 description (OpenAPI 5.28.0): create a Pin](https://developers.pinterest.com/docs/api/v5/pins-create/), checked 2026-10-24): - Every Pin is created on a board, so the request needs a board ID. The title may be up to 100 characters and the description up to 800. - Alt text may be up to 500 characters and the destination link up to 2,048. Both are optional in the API. - Tareno's configuration for Pinterest is stricter than the API: media is required, descriptions stop at 500 characters, and the link goes into its own field. ## Mistakes to avoid - Publishing a cheat sheet with an example you did not run. A wrong command gets saved and trusted for years. - Using a font that only reads on a desktop. Check the image at 200 pixels wide. - Leaving out the tool version. Commands change, and the version makes the sheet honest. - Packing too much into one image. Twelve commands read, forty do not. ## What does not work - Codex cannot judge how the image reads in a Pinterest feed, so a person looks at it at thumbnail size before the draft is requested. - It cannot upload the image into your Tareno library for you unless you do so, because the draft needs a file that is already there. - It cannot publish a pin on its own, since a time request becomes a pin only after you approve it in the Tareno dashboard. ## Frequently asked questions ### Why have Codex run the commands? Because a saved cheat sheet is trusted. Codex runs each command in a scratch environment and compares the output with the text, so the sheet states what it observed, with the tool version, rather than what was remembered. ### What size should the image be? Tareno's configuration recommends 2:3 for Pinterest, for example 1000 by 1500 pixels, in jpg or png up to 20 MB. A tall image takes more room in the feed than a wide one. ### Can Codex check that the image is readable? Not reliably. It can set a large font and a clean layout, but you should open the image at thumbnail size, because that is how most people see it first. ### How should alt text work for a cheat sheet? Pinterest's API description allows up to 500 characters of alt text. Use it to list the sections of the sheet, so a reader who cannot see the image knows what the pin contains and what it links to. ### Can the pin link back to the tutorial? Yes. The link goes into its own field in Tareno's configuration for Pinterest. It gets no automatic preview, so the pin text should say what the tutorial adds beyond the sheet. ### Will the pin appear without my approval? No. A scheduling request is a pending action in Tareno, and Pinterest receives the pin only after you approve it in the dashboard. `get_action_status` shows what happened afterwards. ## Tareno tools used - `list_media` - `get_platform_options` - `create_drafts` - `get_action_status` Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them. ## Related - [Codex × Tareno overview](https://tareno.co/agents/codex) - [Pinterest with Tareno](https://tareno.co/channels/pinterest) - [Media library](https://tareno.co/features/media-library) - [Post scheduling](https://tareno.co/features/post-scheduling) - [Codex and ChatGPT setup](https://tareno.co/docs/mcp/openai)