Select evidence
Use approved sources and link cooldowns to avoid repeating the same material.
Source-backed research, AI-assisted drafts, human review, and Threads publishing—inside one workflow you operate yourself.

Real dashboard · sanitized screenshot without credentials
Threads Auto Poster separates research, drafting, quality gates, approval, and publishing so one failed step does not become duplicate publishing or ungrounded content.
Use approved sources and link cooldowns to avoid repeating the same material.
The agent drafts against strategy, source context, and format limits.
The quality gate checks structure, URLs, length, duplication, and pillar rules.
Approval mode is available; an uncertain publish is never retried automatically.
Source health, temporary snapshots, and cooldowns keep content context traceable.
Set themes, language, source policy, promotion, structure, CTA, and format without rewriting the scheduler.
Rejected drafts remain as evidence. Nothing is forced through just to clear a schedule.
Retryable preparation errors run until the slot window ends; uncertain publishes are quarantined.
Configuration, schedules, history, audit, and source registry run on backup-friendly SQLite.
Start with manual review. Enable auto-post only when the workflow and account are ready.
This repository is for operators who need control of the source registry, schedule, database, AI provider, and Threads credentials.
git clone https://github.com/yanstd888/threads-auto-poster.git cd threads-auto-poster cp .env.example .env npm install npm run build npm run start:4000
| Need | Threads Auto Poster |
|---|---|
| Data control | SQLite on your own host |
| Evidence-backed drafts | Source registry + context |
| Human review | Approval mode |
| Uncertain publish | Never auto-retry |
Build a product education rhythm without losing final approval.
Operate distinct source pools and content pillars in a structured way.
Use research trails, audit logs, and safe fallbacks for accountable content.
No. This is a self-hosted project. You run the app, database, and configuration on your own infrastructure.
Yes. Use approval mode to save drafts and review them before publishing.
No. GitHub Pages is a static introduction site. The scheduler runs on a self-hosted installation.
Read CONTRIBUTING, open a relevant issue, then submit a small PR with appropriate test evidence.