Post to Dev.to from Codex

Codex can publish articles to Dev.to through Postiz. Install the Postiz skill or add the Postiz MCP server to Codex, connect your Dev.to account in Postiz, then give Codex a markdown file or a topic. It writes or reuses the article, uploads the cover image, sets tags, canonical URL, and organization, and schedules it.

Setup Guide GitHub

Please make sure there is always a human in the loop.

Last updated: September 2026

How do I post to Dev.to from Codex?

Set up Codex once with the Postiz skill or the Postiz MCP server, connect Dev.to in Postiz, then ask. The whole setup takes a few minutes.

Setup, then just ask

# One-time setup, option A: Postiz skill + CLI
npx skills add gitroomhq/postiz-agent
export POSTIZ_API_KEY=your_api_key   # or: postiz auth:login

# One-time setup, option B: Postiz MCP server (OAuth, no key)
codex mcp add postiz --url https://mcp.postiz.com/mcp-oauth-dynamic
codex mcp login postiz

# Then just ask Codex:
> Publish my article on Dev.to with
  a cover image and tags, tomorrow at 9am

Codex: Done! Your Dev.to post is scheduled.

Dev.to-Specific Features

👨‍💻

Developer Articles

Publish technical articles with full Markdown support including code blocks, syntax highlighting, and embedded content.

🏢

Organization Posting

Publish articles under your Dev.to organization. Share content on behalf of your team or company with a single setting.

🖼

Cover Images

Upload and attach eye-catching cover images to your articles. Stand out in the Dev.to feed with visual content.

🔗

Canonical URLs

Set canonical URLs to link back to your original content. Perfect for cross-posting from your personal blog without SEO penalties.

🏷

Smart Tagging

Add up to 4 tags per article to reach the right developer audience. Tags drive discoverability on the Dev.to platform.

📅

Scheduled Publishing

Schedule articles for future publication with precise timestamps. Plan your developer content calendar ahead of time.

How does Codex post to Dev.to?

You describe what you want in plain language and Codex handles the Postiz calls for you. Here is how a typical conversation goes.

Find Your Dev.to Integration

Ask Codex whether your Dev.to account is connected. It also checks which options the platform supports.

Example conversation

> Is my Dev.to account connected to Postiz?

Codex: Yes — your Dev.to account is connected
  and ready. Want me to post something?

Prepare Your Content

Write your article in Markdown. Dev.to supports rich formatting including headers, code blocks with syntax highlighting, images, and liquid tags.

Example conversation

> Draft a Dev.to post about our new
  feature launch

Codex: Here's a draft for Dev.to:
  "We just shipped something big..."
  Want me to add media and schedule it?

Publish Your Article

Create a post with your article content, title, cover image, tags, and optional organization and canonical URL settings.

Example conversation

> Yes — add screenshot.png and schedule
  it for tomorrow at 9am

Codex: Done! Scheduled on Dev.to for
  tomorrow at 9:00 AM.

Dev.to Settings Reference

Mention any of these in plain language and Codex sets them for you. These are the Dev.to options it can apply to any post.

Field	Type	Required	Description
`__type`	string	Yes	Must be "devto"
`title`	string	Yes	Article title (min 2 characters)
`main_image`	object	No	Cover image: {id: string, path: string}
`canonical`	string	No	Original URL for canonical link
`organization`	string	No	Organization ID to publish under
`tags`	array	No	Up to 4 tags: [{value: string, label: string}]

Common Configurations

Ask Codex for any of these common Dev.to publishing scenarios and it applies the matching settings.

Simple Developer Article

Just ask

> Post it with: Simple Developer Article

Codex: Got it. Applying:
  title: 10 TypeScript Tips You Need to Know
  tags: TypeScript, JavaScript, Web Dev, Programming

Organization Post with Cover Image

Just ask

> Post it with: Organization Post with Cover Image

Codex: Got it. Applying:
  title: Introducing Our New AI Scheduling Tool
  main_image: id=img-abc123, path=https://uploads.postiz.com/launch-cover.png
  organization: my-org-id
  tags: AI, Show Dev, Productivity

Cross-Posted Article with Canonical URL

Just ask

> Post it with: Cross-Posted Article with Canonical URL

Codex: Got it. Applying:
  title: How We Reduced Build Times by 80%
  canonical: https://engineering.mycompany.com/build-times
  tags: DevOps, CI/CD, Performance

Full-Featured Article

Just ask

> Post it with: Full-Featured Article

Codex: Got it. Applying:
  title: Building a Real-Time Dashboard
  main_image: id=img-xyz789, path=https://uploads.postiz.com/dashboard.png
  canonical: https://myblog.dev/real-time-dashboard
  organization: my-team-id
  tags: React, WebSockets, Tutorial, JavaScript

What is Codex?

Codex is OpenAI's coding agent. It runs as the Codex CLI in your terminal (npm install -g @openai/codex), as an IDE extension, and in the cloud, and it can run shell commands and call MCP servers, which is how it drives Postiz. Codex is not ChatGPT: ChatGPT is the chat assistant on chatgpt.com and connects to Postiz differently (see the ChatGPT guide). For the full setup, start at the Codex + Postiz hub.

💻

Terminal & IDE Native

Codex runs in your terminal or IDE. You type what you want in plain English and it handles Postiz for you — no extra configuration needed.

🔧

Autonomous Execution

Codex runs commands inside a sandbox with approval rules you control, and works through multi-step tasks like discovering channels, uploading media, and scheduling Dev.to posts.

⚡

Parallel Tasks

Run multiple Codex tasks simultaneously. Schedule posts to different platforms in parallel while Codex handles other coding work.

How Postiz Works with Codex

Codex discovers Postiz two ways: the postiz skill, which it loads from .agents/skills or ~/.agents/skills and which you can invoke with $postiz, or the Postiz MCP server added with codex mcp add. Either way it learns the available tools and chains them for Dev.to workflows.to articles with the right settings.

✓Install the Postiz skill with npx skills add, or add the Postiz MCP server with codex mcp add
✓Codex loads skills from .agents/skills and reads SKILL.md to learn the Postiz CLI
✓Authenticate with POSTIZ_API_KEY or postiz auth:login; the MCP route uses OAuth instead
✓Codex runs commands in its sandbox and asks for approval based on your permission settings
✓Works alongside your coding tasks in parallel

Install Postiz

# Install the Postiz skill
npx skills add gitroomhq/postiz-agent

# Set your API key
export POSTIZ_API_KEY=your_api_key

# Or add the Postiz MCP server instead (OAuth, no API key)
codex mcp add postiz --url https://mcp.postiz.com/mcp-oauth-dynamic
codex mcp login postiz

# Then ask, interactively or headless
codex "list my social media integrations"
codex exec "post today's changelog to Dev.to"

Dev.to Publishing with Codex

Tell Codex what to post from your terminal or IDE — it discovers your integrations via Postiz and handles the entire publishing workflow.to integration, and handles the entire publishing workflow autonomously.

💻

Just Ask Codex

Terminal and IDE integration

Tell Codex what to post from your terminal or IDE — it discovers your integrations via Postiz and handles the entire publishing workflow.

Codex CLI

$ codex "Post to Devto about our
  new feature launch, schedule for
  tomorrow at 9am"

Codex: I'll handle that.
  Found your Devto integration.
  Composing and scheduling the post.

  Done! Your post is scheduled.
  Post ID: abc-123

💻

Parallel Tasks

Multiple tasks at once

Codex can handle multiple tasks in parallel. Schedule posts to different platforms while it works on other coding tasks simultaneously.to automatically — no manual trigger needed.

Codex Parallel Tasks

# Run multiple posting tasks in parallel
$ codex "Schedule a post about our
  launch to X for tomorrow 9am" &

$ codex "Write a LinkedIn article
  about our new feature and schedule
  for tomorrow noon" &

$ codex "Fix the bug in auth.ts"

# All three tasks run simultaneously

Why Codex + Postiz for Dev.to

Codex's autonomous execution makes Postiz a natural fit. The agent reads the SKILL.md to understand every available command, then autonomously chains them together for Dev.to workflows.

✓Runs in your terminal or IDE — just type what you want
✓Autonomous execution in sandboxed environments
✓Parallel task support — post while coding
✓Cover images uploaded and attached automatically
✓Cross-post to Dev.to + other platforms in a single session
✓Powered by OpenAI's most capable models

SKILL.md (loaded by Codex from .agents/skills)

---
name: postiz
description: Social media automation
  CLI for scheduling posts across
  30+ platforms including Dev.to
homepage: https://docs.postiz.com/public-api/introduction
---

# Loaded by Codex from .agents/skills
# Invoke explicitly with $postiz

# Available Commands
- postiz integrations:list
- postiz integrations:settings <id>
- postiz posts:create
- postiz upload <file>
- postiz analytics:platform <id>

# Dev.to Settings
title, main_image, canonical,
organization, tags

Also Works with Claude Code

Postiz works with any AI agent that can run commands or call MCP tools — you ask, the agent does the work. That includes Anthropic's Claude Code: see the Claude Code Dev.to guide, or the Postiz Agent page for any other agent.

Claude Code

by Anthropic

Claude reads the Postiz skill so it knows what it can do, then autonomously discovers your Dev.to integration, uploads your cover image, applies tags and organization settings, and publishes the article.

Claude Code

> Publish my React tutorial to Dev.to
  under our org with a cover image,
  tag it with react and webdev

Claude: Done! Scheduled on Dev.to for
  tomorrow at 9:00 AM.

Can Codex post to Dev.to and other platforms at once?

Publish the same article to Dev.to and other platforms in a single request. Each platform gets its own settings.

Example

> Post "Excited to announce our new feature!" to
  Dev.to and LinkedIn tomorrow at 9am, then schedule
  a daily tip on Dev.to every weekday at 10am

Codex: Done! Scheduled:
  - Dev.to + LinkedIn: tomorrow 9:00 AM
  - Daily tips on Dev.to: Mon-Fri 10:00 AM

What can I ask Codex to post on Dev.to?

Codex takes plain-English prompts in an interactive session, as a one-off codex exec command, or through the $postiz skill. These are the kinds of prompts people type for Dev.to.

Prompts for Dev.to

> Publish ./posts/mcp-tutorial.md to Dev.to with cover ./assets/cover.png
  and tags webdev, ai, tutorial, tomorrow 9am

$ codex exec "Cross-post our latest blog article to Dev.to under the
  Postiz organization with the original URL as canonical"

> $postiz Turn this week's merged PRs into a Dev.to changelog
  article and schedule it for Friday

What Dev.to rules should Codex follow?

These are the Dev.to limits and required settings Postiz enforces. Codex reads them from postiz integrations:settings, and you can mention any of them in your prompt.

✓title is required, at least 2 characters.
✓Dev.to allows up to 4 tags per article.
✓The cover image goes through postiz upload, then main_image takes its id and path.
✓canonical and organization are optional; organization ids come from postiz integrations:settings.

Codex and Dev.to FAQ

How do I post to Dev.to from Codex?

Install the Postiz skill with npx skills add gitroomhq/postiz-agent, or add the Postiz MCP server with codex mcp add postiz --url https://mcp.postiz.com/mcp-oauth-dynamic. Connect Dev.to in Postiz once, then ask Codex in plain English what to post and when. Codex resolves the Dev.to settings, uploads any media, and schedules the post.

Can Codex publish under my Dev.to organization?

Yes. Connect Dev.to in Postiz and Codex reads your organizations through postiz integrations:settings, then fills the organization setting with the matching id when you name it. Leave it out and the article publishes on your personal profile. Tags, cover image, and canonical URL work the same either way.

How many tags can Codex add to a Dev.to article?

Up to four, which is Dev.to's limit. Codex picks tags from your prompt or suggests relevant ones from the article text, using lowercase single words as Dev.to expects. It also uploads your cover image with postiz upload and sets the canonical URL if you are cross-posting from your own blog.

Can Codex post to Dev.to on a schedule without me watching?

Yes. Postiz stores scheduled Dev.to posts and publishes them at the chosen time, so Codex does not need to stay open. For unattended runs, call codex exec with your prompt from a script or cron job. Keep a human reviewing the output, since Codex will publish exactly what it is told to publish.

Do I need a Postiz API key to post to Dev.to from Codex?

Not with the MCP route. Run codex mcp login postiz and Codex signs in to your Postiz account over OAuth, so it only reaches channels you already connected, including Dev.to. The CLI skill route needs either postiz auth:login or a POSTIZ_API_KEY environment variable. Your Dev.to login itself never leaves Postiz.

Is posting to Dev.to from Codex the same as posting from ChatGPT?

No. Codex is OpenAI's coding agent for your terminal and IDE, and it reaches Postiz through the Postiz skill or MCP server. ChatGPT is the chat assistant on chatgpt.com, which connects to Postiz as an app or custom MCP connector. Both can publish to Dev.to; see the ChatGPT guide for that setup.