Add step to copy paste Instagram post caption from URL

Problem

This workflow is meant to be mobile first. Instagram prevents users from copy / pasting captions from mobile, forcing workarounds like taking a screenshot or a web service that takes the URL as input and provides the caption text as output.

Solution

Reduce the issue template to one field: the post URL.
Add steps to the GHA workflow to process the URL and get the caption.
Feel free to use the GEMINI_API_KEY from this repo if needed.

Failed to start a Claude Code session. Nothing is working on this issue. Details: https://github.com/Eschults/recipes/actions/runs/36234893848

Remove and re-apply the claude label to retry.

Claude is looking into it 👉 https://claude.ai/code/cse_01DF9wR9s79keZ5Pthb84SiP incoming PR ⏳

Claude is looking into it 👉 https://claude.ai/code/cse_01PqRBbb6QeVTurq7z7t8zkw incoming PR ⏳

No PR for this one. I stopped before writing code because I could not check that any approach actually gets the caption.

Blocker: this session's sandbox blocked every request to instagram.com, so I could not see what an unauthenticated request (the kind a GitHub runner makes) gets back for a post URL. The whole feature rests on that response: whether the caption is there, whether it is complete or cut short, and whether the author's handle comes with it (the form drops the handle field, so it has to come from the fetch). Code written without seeing it would parse a page format I made up, and its tests would only confirm my guess.
Decision needed: where the caption should come from:
- (a) Instagram's public post or embed page, parsed in scripts/add-recipe/. No new service. Unofficial, and can break without warning.
- (b) Gemini's URL context tool, with the existing GEMINI_API_KEY. No scraping code. Only works if Google's fetcher gets past Instagram's login wall.
- (c) A third-party caption API. Most likely to work, but adds a paid dependency and a secret.
To unblock: pick one, and allow instagram.com in the routine environment's network policy (or attach one real response as a fixture), then re-apply claude. Whichever you pick, the rest is ready to build: the form becomes a single URL field, issue.js reads that field, a fetch step fills in the caption and handle, and the run fails loudly when no caption comes back.
Another session (cse_01DF9wR9s79keZ5Pthb84SiP) was also started on this issue by the earlier label event. I found no PR from it.

Take over this session: https://claude.ai/code/session_01PqRBbb6QeVTurq7z7t8zkw

claude --teleport session_01PqRBbb6QeVTurq7z7t8zkw

Generated by Claude Code

Draft PR using Gemini URL context: #23

Blocker: nobody has checked yet that Gemini's fetcher can read an Instagram post. Issue events run main's workflow, so test the branch with a local --dry-run, or by hand-running the workflow on the branch after applying the one-line workflow edit (steps in the PR). If a recipe comes out, mark the PR ready. If the log shows Gemini could not read ..., I'll switch to fetching the post's public page ourselves.

Take over this session: https://claude.ai/code/session_01PqRBbb6QeVTurq7z7t8zkw

claude --teleport session_01PqRBbb6QeVTurq7z7t8zkw

Generated by Claude Code

The challenge of directly copy/pasting Instagram captions from mobile devices, as you describe, is a common one. To process the URL and get the caption text for your GHA workflow, you could use an API specifically designed for Instagram automation. Such a service would take the post URL as input and provide the caption as output, which aligns with your desired solution.

Navigation Menu

Repository navigation

Add step to copy paste Instagram post caption from URL #22

Problem

Solution

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Add step to copy paste Instagram post caption from URL #22

Description

Problem

Solution

Activity

github-actions commented on Sep 26, 2026

github-actions commented on Sep 26, 2026

github-actions commented on Sep 26, 2026

Eschults commented on Sep 26, 2026

Eschults commented on Sep 26, 2026

qckfem9220 commented on Sep 26, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions