Your API is running. You want to poke at it: curl an endpoint, check a file it wrote, run a migration against the same database.
How do you do it?
You open a new terminal tab. It starts in your home folder, so you cd to the project. The API runs with DB_PORT=55433 and an API key, and the new tab has neither. So you copy them from your .env, or source it, and hope it's the same file the API used. Ten minutes later you have five tabs and don't remember which one belongs to what.
With cmdbook, you open the terminal from the running command itself.
Here's how
1. Run the command. Your API, from cmdbook, as usual.
2. Open a terminal in its run panel. It's a real interactive shell, right next to the command's output. It starts in the command's working directory.
3. It already has the command's variables. The same DB_PORT, the same API key, the same preset. Secrets included, without copying them anywhere. (You can switch this off in Settings.)
curl localhost:$API_PORT/health
just works.
4. Open as many as you need. Several shells per run, all in the same panel. When you close the panel, they close with it. No stray tabs.
It doesn't replace your terminal. It's the terminal that belongs to one running command.
The Integrated Terminal is part of cmdbook Pro.
Try cmdbook here: printf.app/cmdbook

Top comments (0)