Dirpush
Submit your product to startup and SaaS directories with your own coding agent, and keep track of every submission on your own machine.
Dirpush is local-only. The dirpush CLI gives your agent a durable job queue, a verified registry of directories with playbooks, and your product's facts. The agent drives a browser on your computer, and a localhost dashboard shows what is live, what is pending and what needs you. There is no server and no account, and nothing leaves your machine unless you choose to share it.
Browse the registry at dirpush.com: every directory with its cost, its link type (dofollow, nofollow, ugc or sponsored, measured on real listing pages) and how to submit.
Setup
Requires Bun and Google Chrome. Hand it to the agent you already use: any coding agent or computer-use bot that can run shell commands. It's tested with Claude Code and Codex. Agents drive their own Chrome profile with agent-browser, never your everyday browser, and saved passwords are filled by the CLI so they never pass through the model.
npm i -g dirpush agent-browser # or run everything below with npx
dirpush init acme # sets up ~/.dirpush and installs the agent skill
init keeps your launch in ~/.dirpush (database, product files, the agents' Chrome profile) and installs the dirpush skill for your agents in ~/.claude/skills and ~/.agents/skills. That's the only command you need.
Talk to your agent
| Say | What happens |
|---|
| "set up dirpush" | It fills in your product's facts with you and checks its tools (an email tool for verification links, the browser). |
| "continue my launch" | It finds directories that fit, submits, verifies emails, re-checks pending listings, and records everything. |
| "what do you need from me?" | It walks you through the few things only you can do, one at a time: sign into Google once, tick a bot check in a window it opens, rarely submit a site by hand. You answer "done" and it carries on. |
| "how is my launch going?" | Live, pending and rejected listings, and what's waiting. |
Agents never solve CAPTCHAs, never pay, and ask before anything your permissions.yaml marks as "confirm". dirpush serve opens a local dashboard if you want to look around.
The CLI, if you want it
Agents drive everything below; you never have to. dirpush help lists it all.
| Command | Purpose |
|---|
dirpush actions | What's waiting on you |
dirpush handoff | Walk your part yourself in the terminal instead of in chat |
dirpush submissions list --product <id> | Every submission and its outcome |
dirpush directories recommend --free --unsubmitted --product <id> | Directories that fit and haven't been tried |
dirpush registry updates [--apply] | Update your registry from the published one on dirpush.com |
dirpush dr show | Domain Rating history (optional, needs AHREFS_API_KEY) |
Working on dirpush
git clone https://github.com/baronunread/dirpush.git && cd dirpush
bun install --frozen-lockfile
bun launch init acme # a git checkout keeps its data in the repo (data/, workspace/)
bun run dev # dashboard on localhost
bun run verify # repo checks, typecheck, tests
Releases publish to npm from GitHub Actions when a v* tag is pushed (trusted publishing, no token).
Repository layout
| Path | Contents |
|---|
src/ | CLI, job queue, registry, dashboard server and UI |
registry/ | Verified directory definitions, playbooks and source provenance |
site/, scripts/build-site.ts | The static dirpush.com site |
scripts/ | Registry and site builds, repository checks |
docs/ | Plan, operator guide and architecture |
data/, workspace/ | Your private local state, excluded from Git |
Contributing
Know a directory that's missing, or one whose details are wrong? Open an issue with its URL. Pull requests that add or fix a directory in registry/directories/ are welcome; run bun run verify first.
License
- Code: MIT.
- Registry data (
registry/, and registry.json on dirpush.com): CC BY 4.0. Reuse it freely with credit to dirpush.com.
Third-party code and the directory seed lists keep their own licenses; see third-party notices.
