Skip to content

PUBLISHING.md

Latest commit

 

History

History
86 lines (56 loc) · 2.01 KB

PUBLISHING.md

File metadata and controls

86 lines (56 loc) · 2.01 KB
Raw

Publishing Guide

Recommended Positioning

Lead with the problem, not the implementation detail.

Good positioning:

  • Persistent native cron for long-running Codex CLI agents
  • Keep recurring work in the same Codex thread
  • Native cron for Codex CLI without drifting into automation

Bad positioning:

  • A random plugin bundle for my Codex fork
  • Some scripts for cron

Suggested Repo Description

Persistent native cron for long-running Codex CLI agents. Keep recurring work in the same thread without falling back to automation.

Suggested Topics

  • codex
  • codex-cli
  • cron
  • scheduler
  • agent
  • ai-agent
  • developer-tools
  • productivity
  • automation

Suggested Repo Name

Pick one and stay consistent everywhere:

  • codex-thread-cron
  • codex-agent-cron
  • codex-native-cron

codex-thread-cron is the clearest if the core value is "same thread, not automation."

What To Put In The Social Preview

Use one sentence only:

Make Codex CLI wake itself up later and keep working in the same thread.

If you create a social preview image, keep it simple:

  • one bold title
  • one terminal screenshot
  • one short subtitle

Do not make it look like a generic AI poster.

Release Checklist

  1. Run ./scripts/release-check.sh
  2. Verify the README still matches actual install behavior
  3. Confirm the repo root works with codex marketplace add <repo-root>
  4. Tag a release that matches CHANGELOG.md
  5. Publish a short demo in the README or release notes

Launch Post Angle

Focus on one sentence:

Codex is great in-session, but weak at recurring thread-local work. This project adds native cron packaging so Codex can wake itself up later and continue in the same thread.

Then show:

  • one concrete use case
  • one install command
  • one limitation

That is usually enough. Do not oversell.

Suggested Demo Flow

  1. Open Codex CLI in a repo
  2. Ask it to create a weekday review cron
  3. List the cron jobs
  4. Show the persisted config and smoke check
  5. Show the next wake-up returning to the same thread