Frequently asked questions about LaunchRepo

Access to a private GitHub repository. You clone it and use everything locally with your own agent: the directory catalog, a playbook for every directory, your product brief, the submission tracker and a local dashboard. No SaaS, no extra login, nothing uploaded to us.

Because the value isn’t the list of directories — anyone can find a list. It’s the hand-written playbook behind every directory: which route to take, what each field expects, where the traps are and what to do when something goes wrong. Without it, your agent guesses and burns tokens on trial and error. With it, it follows a tested path, submits properly and records every result, so nothing gets lost or submitted twice.

Setup is a one-time first session that establishes your workspace, browser connection and run target; later sessions reuse it. After that, plan roughly 3–5 minutes per directory. What your agent costs depends on your provider and plan, so check its billing before buying.

Plan on roughly 3–5 minutes per directory. It depends on whether you already have an account there, whether you sign in with Google or with email and password (which adds a confirmation email), and how many forms the directory has. With enough hardware, you can run up to two agent sessions in parallel.

Any agent that can read local files and drive a browser you are signed in to. Claude Code, Codex and Cursor meet those two requirements once their browser integration is set up; we publish no benchmark and certify no configuration. The capability check on the how-it-works page tells you whether yours is ready before you pay.

BROWSER-SETUP.md walks you through connecting your agent to a Chrome you can see: Chrome DevTools MCP attached to your logged-in browser, or an isolated profile via CDP as a fallback, plus a supervised smoke check. That way OAuth logins, email confirmations and CAPTCHAs happen in your own session.

Locally. The tracker, the record script and the dashboard are Python 3.10+ standard library on Windows, macOS or Linux, run on your machine, and the dashboard binds to 127.0.0.1 only. Your product facts, accounts and results stay in a private workspace next to the delivery checkout; nothing is uploaded to us.

English. The website exists in several languages, but the playbooks, agent instructions and the local dashboard in the repository are English — which is what coding agents handle best. Your product copy can be in any language a directory accepts.

You need to be comfortable running a coding agent, using Git and following a setup guide for connecting the agent to Chrome. No code has to be written; the local dashboard covers the forms.

It creates more relevant places where your product may be discovered and gives you a clean record of what was submitted, approved and published. We have not measured attributable traffic, rankings or customer growth, and no platform, backlink or outcome is guaranteed.

No specialist SEO knowledge is required to run the workflow. Your agent checks fit and current rules, while the tracker separates attempts from public listings. Whether a published page links, ranks or sends visitors must be measured after it goes live.

Unlikely, and that’s built into how free directories work. Free listings wait in a review queue, so they go live anywhere from one day to about twelve weeks after you submit. The links arrive one by one over a long period, not as a sudden spike. How Google weighs any single link is up to Google.

Largely automated. Your agent creates the account, confirms the verification email, fills in the forms and submits the listing on its own. It hands you CAPTCHAs, two-factor codes and logins it can’t complete (see below) and stops before anything that would cost money.

Some directories show a CAPTCHA. Your agent pauses there, you solve it once in your own browser, and it carries on. Most directories have none at all. Don’t want to deal with any? Tell your agent at the start and it filters those directories out automatically.

Your agent drives a real Chrome browser and reads every page the way a person does, instead of clicking hard-coded selectors that snap with the next redesign. That’s our secret sauce: each playbook describes what the directory needs and what a finished submission looks like, not which pixel to click. A moved button or a reworked form doesn’t stop it. When a directory changes more than that, we re-test the route and publish the updated playbook for every buyer.

Yes: ask your agent to prepare drafts and withhold submission permission until you review them. You can also grant permission for final submissions in advance. These permissions are instructions for your agent, rather than a software-enforced approval gate.

No. You operate your own agent and accounts using the supplied files, guides and local tooling. Nobody at The CodeCave submits anything for you, and no accounts are created on your behalf.

There is no AI agent in the box — you bring your own and pay its usage to your provider. Directory fees, hosting and third-party services are not included, and no listing, traffic or ranking is guaranteed.

No. As of October 7, 2026, the catalog has 299 active guides: 84 routes verified as free, 156 conditional-free routes whose prerequisites are shown before work starts, 5 research-only routes and 53 currently unavailable routes. 50 known mandatory-paid routes are excluded from active recommendations. Unknown is never treated as free, and every route is rechecked for fit, access and current terms before submission.

Check the platform’s edit controls or contact its support through your own account, then record the correction request and check the public page again. Availability and timing depend on the platform. LaunchRepo does not automatically remove or change third-party pages.

Your workspace holds the product records locally. Your chosen AI provider, connected browser tools and destination websites process data as you use them. Authorize only the browser and verification-email scope you want your agent to use.

Yes, for products you or your company own, with repository access bound to one GitHub account. Client work requires a separate license. Redistribution is not included.

As many as you like — there’s no limit. Buy once and use it for all of your own products, as often as you want, for good. Client work needs a separate license.

Yes. You pay once and keep the repository — no subscription, no renewal, no per-launch fee. The only running cost is your AI agent’s usage, which your provider bills you for directly.

No. The regular price is €139, an automatic €20 discount applies at checkout, and you pay €119 once. The price does not rise with the number of sales.

Your agent’s usage, billed by your provider. The default queue contains only currently evidenced zero-cost routes; conditional routes show their prerequisites first. Optional featured placements and fast lanes are outside that queue, and the workflow never authorizes a purchase for you.

No. LaunchRepo is digital content delivered immediately after payment; by buying you request immediate delivery and lose the right of withdrawal once access is delivered, except where mandatory law applies. Read the sample guide and the setup check before you buy.

The reference price on the site includes 19% German VAT. Stripe determines the tax that applies to your country at checkout and shows the final amount before you pay; valid business tax details can change the amount.

Yes. Buyers and creators earn 30% of the net price of every sale they refer, and the people who buy through their link save €20. Details and the creator application: launchrepo.dev/affiliates/

Yes. One payment, no subscription: every update we publish, including new directories and playbooks, lands in your repository at no extra cost. The changelog shows everything that has shipped so far.

No. Checkout is a Stripe-hosted page: you enter an email and pay. Afterwards you verify that email and connect the GitHub account that should receive access.

As an invitation to a private GitHub repository, sent to the GitHub account you connect after purchase. Accept it, clone the repository and follow onboarding to create a separate private workspace for your products. You keep your local copy.

Fetch updates into a separate clean copy of the delivery repository. Follow the update guide to bring selected reusable kit files into your private workspace, keeping product records, accounts and credentials separate. The changelog shows published changes; there is no promised update schedule.

Email support at info@thecodecave.de on a best-effort basis, without guaranteed response times. It covers the repository and its tooling — not performing submissions, configuring your agent or issues with third-party platforms and accounts.