Attach images from Claude or ChatGPT straight to your Refract posts

Until now, if you wanted an image in a Refract post, created over MCP you had to host it somewhere first and give Refract a public URL to the media. That step is gone for images coming from AI agents. You can now attach images directly from Claude or ChatGPT to a post in Refract, with no public URL needed.

What changed

The image part is what's new. Refract already had a connection to AI agents through MCP, and you may already be using it to draft and manage posts. This update doesn't change that connection. It removes the hosting step for images, so the picture an agent makes can go straight onto your post.

Why it matters

Most of the friction in visual posting comes from small steps: download a file, upload it somewhere, copy a link, paste it in, and check that it loads. Each one is quick on its own, but together they slow down a draft that should be finished in one sitting. Attaching images directly keeps you in the same conversation where you made the image.

It also means you don't need a public address for media you only want to use in a post. If the image is meant for your draft, it can stay out of public view until you publish.

Working with images in a chat

Ask your agent for the image you need and describe what the post is about. Then bring the picture into the draft as part of the same workflow. Look over the text and the image together before you save or schedule anything, just as you would with any other post. You stay in control of what goes out, and nothing is published without your say-so.

What stays the same

Your drafts, your review steps, and your schedule work the way they did before. The only change is how images arrive. Text-only posts are unaffected, and posts that already use images with a public URL keep working.

Where to start

If you already use Claude or ChatGPT with Refract, try attaching an image to your next draft. Compare it with how you handled images before and see how many steps you can skip. Small changes like this add up quickly when you publish across several networks.