Save this if you vibe-code and run your app with Tilt. The agent built the code. Tilt is the part that starts it, watches it, and reloads it. Check these once, then again whenever the setup changes.
- [ ] Tilt is installed and on your PATH. Run
tilt versionin a terminal. - [ ] Docker is running. Tilt builds and runs containers, so it cannot start without Docker.
- [ ] You can open the Tilt dashboard. It runs on port 10350 by default, and it shows every service on one screen.
- [ ] Every resource shows a green status. A yellow or red resource is the first thing to read.
- [ ] You know which files Tilt watches. Check the Tiltfile for the paths, so an agent's edit actually triggers a reload.
- [ ] Generated files are left alone. Edit the source that produces them, not the output.
- [ ] Your secrets are in the environment, not in the Tiltfile or the code.
- [ ] You restart Tilt after changing the Tiltfile. A running session does not pick up every change to the configuration.
- [ ] You read the log for the first error. Not the last. Later errors often come from the first.
- [ ] You stop Tilt when you are finished. A running session holds ports for the next start.
If you use TDK CLI, run tdk doctor --json first, then tdk up. Check tdk status --json once everything is up.
Top comments (0)