Faster Iteration with Reset and CLI Improvements

Ampt is built around the idea that cloud development should feel local. Instant code syncing, production-parity sandboxes, popular framework support, zero infrastructure config. Every feature we ship is in service of that: less time fighting your environment, more time building your app.

Today we're releasing a set of CLI improvements that continue that mission. The headliner is reset, a new way to wipe your environment clean and start fresh without losing your URL or tearing down environments. We've also added params management and whoami directly in the CLI.

Resetting your personal sandbox

Your sandbox is a living environment. As you iterate, run scripts, upload files, execute tasks, and test data operations, artifacts accumulate. Test records pile up in your data table. Uploaded files linger in storage. After enough changes, your sandbox can drift into a state where your app behaves differently than you'd expect from a clean deploy.

The new reset command clears all of that:

bash
ampt reset

This wipes your data table, removes uploaded files from storage, clears the code archive and any cached node_modules, and does a full code re-sync from your local directory. You get a clean environment that matches your current code, without needing to delete and recreate your sandbox.

Running this command will ask for confirmation, or you can pass --yes to skip the prompt.

Reset and AI coding agents

This is especially relevant if you're using AI coding agents. Agents write a lot of code, deploy a lot of changes, and often run tests to verify things are working. All of that activity generates data, files, and state that can accumulate quickly. reset is a perfect companion for that workflow. Let the agent iterate, then clean the slate when you're ready to validate from a known starting point.

Reseeding data after a reset

When you reset your sandbox, your data table is empty. If your app needs seed data to function, you can use the import command to load it from a local JSON file:

bash
ampt import seed-data.json

This makes it easy to get back to a consistent starting state after a reset. You can also use export to dump your current data to a local file at any time, which is useful for capturing a known-good state before you reset:

bash
ampt export snapshot.json

Between reset, import, and export, you have a full cycle: iterate, snapshot if needed, reset, reseed, keep building.

Resetting a preview environment

Preview environments work the same way. When you run share, Ampt copies your sandbox's code, data, and storage files to the preview instance. That's powerful because your preview starts as an exact replica of what you've been developing against.

But after a stakeholder or teammate tests the preview, that environment accumulates its own state. When you're ready to show them the next iteration, you want a clean copy that reflects your current sandbox.

The new --reset flag on share handles this:

bash
ampt share my-preview --reset

This wipes the preview's data and storage, clears the code archive and cached node_modules, then redeploys a fresh copy from your sandbox. The URL stays the same. Anyone you've shared it with still has access. No new links to send, no bookmarks to update.

The workflow becomes: iterate in your sandbox with your coding agent, reset your sandbox when you need a clean slate, share to a preview. Get feedback, iterate again, then share --reset to push a clean version to the same URL.

Managing parameters from the CLI

The params command lets you get, set, and delete app parameters without leaving the terminal:

bash
ampt params get              # list all parameters
ampt params get MY_SECRET    # show a specific parameter's details
ampt params set API_KEY sk-abc123 --description "OpenAI key"
ampt params delete OLD_PARAM

Parameters are the encrypted config values your app reads at runtime (API keys, feature flags, connection strings). Previously you had to go to the dashboard to manage them. Now you can do it inline while you're developing.

The output shows you where each parameter comes from: org level or app level, and whether a local value is overriding an org-level or app-level default. Helpful when you're debugging why your app is picking up one value instead of another.

Who Am I?

whoami shows the currently logged-in user, account details, and every organization you have access to along with your permission level in each:

bash
ampt whoami

Quick sanity check when you're switching between orgs or troubleshooting access issues. It shows your username, email, user ID, account creation date, and a list of your orgs with roles.

We're continuing to optimize the cloud development experience, and these features are part of that push. Whether you're working with an AI agent that's churning through iterations or manually testing a feature with a colleague, the goal is the same: stay in the terminal, stay in flow, and don't waste time on environment management.

All of this is available in CLI version 1.2.0. Your existing CLI will update automatically on your next run, or you can run npm install -g @ampt/cli to manually update.