RepoGo Is Changing

Hi everyone,

RepoGo is changing. A lot.

We're still early, still learning, and figuring out what matters most to the developers using our product.

Over the past few months, we've built some ambitious technology. But as we've learned more, we've realized that building a great product isn't about how many features we can ship. It's about building the right ones.

We're making some significant changes to RepoGo, and we want to be transparent about what's changing, why we're making these decisions, and what they mean for you.

Our priorities moving forward are simple:

Privacy first. Less complexity. More value.

Want to try it now? The next version of RepoGo is open to new users on TestFlight.

Important: Please read before updating

The next version of RepoGo introduces breaking changes that may affect your existing development environments and locally stored work.

If you have repositories stored directly on your iPhone or work inside a Vercel Sandbox created with the current version, please back up your work before updating.

• Commit and push your changes to GitHub or another remote Git repository.
• Back up any untracked files, configuration files, or other important data.
• Verify that your work is accessible outside RepoGo.

Committing locally is not enough. You must push your changes or export a backup to preserve them outside the app.

Existing on-device repositories will no longer be accessible through RepoGo after updating.

Please read the details below before installing the next release.

1. Privacy comes first

The next version of RepoGo will no longer require an account or sign-in.

Your chats, code, and project data will live on your paired development environment, and your chats can never be read, not even by our servers.

Communication between your devices will be end-to-end encrypted. Our relay servers will forward encrypted data without being able to read its contents.

We're also changing how credentials are stored. Credentials used to access server and sandbox environments will be securely stored on your device using Apple's Keychain.

We believe developers should have control over their development environments and data without having to trust another company to store their work.

Your machine. Your agents. Your data.

2. A simpler, more focused RepoGo

We're making some difficult decisions about what we maintain.

In the next release:

• No more accounts or sign-in. Open RepoGo, pair your environment, and start working.
• Local data ownership. Chats and project data will live on your paired environment.
• Web version discontinued. We're focusing on the native iOS experience.
• Leaderboard and Shipping Map removed. We're simplifying the experience around the features developers actually use.
• Cursor and GitHub Copilot agents removed. We're narrowing our support to Claude Code and OpenAI Codex.
• Grok Voice and Gemini Voice removed. Voice functionality will focus on OpenAI using your own API key.
• Existing Vercel Sandboxes left behind. Vercel Sandboxes are still supported with credentials kept on your device, but sandboxes created with the current version will no longer be reachable through RepoGo.
• On-device repositories removed. Existing repositories stored directly on your iPhone will no longer be accessible through RepoGo.

These decisions aren't about abandoning our ambitions.

They're about focusing our engineering efforts on delivering the best possible experience with the tools developers actually use.

Technical debt is inevitable. But we believe that complexity should come from features that provide real value, not simply from things we're capable of building.

3. Changes to RepoGo Free and Pro

We're also rethinking what should be free and what belongs in RepoGo Pro.

Previously, RepoGo required an upgrade to run multiple coding agent sessions.

Starting with the next release, unlimited coding agent sessions will be free for everyone.

We believe developers should be able to work with their coding agents without paying RepoGo just to open another session.

Here's what the new plans will offer:

RepoGo Free

• Unlimited Claude Code and Codex agent sessions.
• Voice using your own OpenAI API key, limited to one voice session and 5 minutes per day.
• One paired development environment.
• Standard localhost browsing allowance.

RepoGo Pro — $9/month

• Everything in Free.
• Unlimited voice orchestration using your own OpenAI API key.
• Multiple paired development environments.
• Public development tunnels lasting up to 6 hours.
• Higher localhost traffic allowances.

Any charges from Claude Code, Codex, or your OpenAI API usage remain separate from RepoGo.

Our goal is simple: keep the core coding experience free, and charge for additional capabilities that provide meaningful value or have ongoing operating costs.

We want RepoGo Pro to be worth paying for without making the free experience feel unnecessarily restricted.

4. A new way to install the RepoGo Host

We're changing how the RepoGo Host is distributed.

Previously, the macOS host was installed using a downloadable DMG.

Starting with the next release, you'll install and run the host directly from your terminal:

npx @repogo/host

This simplifies installation and provides a more consistent experience across supported development environments.

Existing users will need to install the new host and pair their devices again.

The previous host version will not be compatible with the new architecture.

5. Important: Changes to Vercel Sandboxes

Vercel Sandboxes are still supported in the next version of RepoGo. Your Vercel credentials will be stored on your device in Apple's Keychain instead of on our servers, and you'll connect your Vercel account again after updating.

Sandboxes created with the current version of RepoGo will not carry over. They will no longer be reachable from the new version of the app.

However, those existing sandboxes will remain associated with your Vercel account and may continue to be accessed and managed through Vercel, subject to Vercel's sandbox lifecycle and retention policies.

RepoGo will not delete your Vercel sandboxes as part of this transition.

We strongly recommend that you commit and push any important work to GitHub or another remote repository before updating.

Please also back up untracked files, environment configurations, and anything else that isn't included in your Git repository.

6. Important: Changes to on-device repositories

We've previously supported repositories stored directly on your iPhone, allowing you to work on projects without connecting to another development environment.

In the next release, existing on-device repositories will no longer be accessible through RepoGo.

If you have important work stored locally on your iPhone, please take action before updating.

Before installing the next version:

1. Open any repositories stored locally in RepoGo.
2. Commit any changes you want to preserve.
3. Push those commits to GitHub or another remote Git repository.
4. Back up untracked files, environment configurations, and anything else not included in your commits.
5. Verify that your changes have been successfully saved outside the app.

Any work stored exclusively inside RepoGo on your iPhone may become inaccessible after updating.

We want to give everyone advance notice so there's time to preserve important work.

7. Important changes to your existing account

Because we're removing accounts entirely, we'll also be retiring our existing account infrastructure.

14 days after the new version of RepoGo is released:

• Existing RepoGo accounts and associated user data stored on our servers will be deleted.
• Older versions of RepoGo will stop working.
• You'll need to update RepoGo and install the new host to continue using the app.
• Existing hosts will need to be paired again.

If you have conversations, files, or other important data stored in the current version, please preserve anything you want to keep before the transition.

We'll provide additional migration instructions when the update becomes available.

Our Terms of Service and Privacy Policy will also be updated to reflect these changes.

8. What about running projects directly on iPhone?

We've managed to get Node.js, Next.js, and development servers running directly on an iPhone.

It's some of the most interesting engineering we've done, and something we're genuinely proud of.

But we've been asking ourselves an important question:

Just because we can build something, does that mean we should maintain it for years?

Maintaining an entire development runtime is a significant long-term commitment.

For now, we're removing on-device repository support as we focus on development environments paired with RepoGo.

That doesn't mean we've ruled out bringing local development back in the future.

If developing directly on your iPhone is something you'd genuinely use, we'd love to hear from you.

Your feedback will help shape that decision.

9. Staying in touch

As we're removing accounts entirely, we'll soon have no way to reach you through your RepoGo account, apart from any necessary notices about the transition.

14 days after the new version launches, your existing account and associated server-stored user data will be deleted.

But this doesn't mean goodbye.

If you'd like to continue following RepoGo's development, future releases, and what we're building next, you're welcome to join our newsletter.

Subscribing is completely optional and separate from your RepoGo account.

We won't automatically transfer your account email address to our newsletter.

10. We're still learning

RepoGo is early, and we're learning from every release, every conversation, and every developer who gives us a chance.

Some of the things we've built have been technically impressive. Others have taught us valuable lessons about what really matters.

We built custom loading spinners, and later replaced them with the standard iOS activity indicator. We built entire features, like the Shipping Map, and later removed them. Each one took real time, and each one was something we then had to maintain, test, and eventually delete.

If there's one thing we hope other builders take from this, it's to stay lean. Ship the smallest thing that solves the problem, watch how people use it, and only then decide what deserves more.

We're learning that building more doesn't always mean building better.

And sometimes making a product better means being willing to remove things you've spent months creating.

Our mission hasn't changed:

Make it easier for developers to work with their coding agents from anywhere.

We're simply becoming more intentional about how we get there.

If there's something you love about RepoGo, something you'll miss, or something you think we should do differently, please get in touch.

We're listening.

Thank you for being early with us, for trying RepoGo, and for supporting what we're building.

We're just getting started.

Jerrick Founder, RepoGo