tilt▌
0xbigboss/claude-code · updated Apr 8, 2026
Before investigating issues or verifying deployments, check resource health:
Tilt
First Action: Check for Errors
Before investigating issues or verifying deployments, check resource health:
# Find errors and pending resources (primary health check)
tilt get uiresources -o json | jq -r '.items[] | select(.status.runtimeStatus == "error" or .status.updateStatus == "error" or .status.updateStatus == "pending") | "\(.metadata.name): runtime=\(.status.runtimeStatus) update=\(.status.updateStatus)"'
# Quick status overview
tilt get uiresources -o json | jq '[.items[].status.updateStatus] | group_by(.) | map({status: .[0], count: length})'
Non-Default Ports
When Tilt runs on a non-default port, add --port:
tilt get uiresources --port 37035
tilt logs <resource> --port 37035
Resource Status
# All resources with status
tilt get uiresources -o json | jq '.items[] | {name: .metadata.name, runtime: .status.runtimeStatus, update: .status.updateStatus}'
# Single resource detail
tilt get uiresource/<name> -o json
# Wait for ready
tilt wait --for=condition=Ready uiresource/<name> --timeout=120s
Status values:
- RuntimeStatus:
ok,error,pending,none,not_applicable - UpdateStatus:
ok,error,pending,in_progress,none,not_applicable
Logs
tilt logs <resource>
tilt logs <resource> --since 5m
tilt logs <resource> --tail 100
tilt logs --json # JSON Lines output
Trigger and Lifecycle
tilt trigger <resource> # Force update
tilt up # Start
tilt down # Stop and clean up
Running tilt up
Follow zmx skill patterns — check for existing sessions, derive name from git root, use zmx run (not attach):
PROJECT=$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" || basename "$PWD")
SESSION="${PROJECT}-tilt"
if zmx list --short 2>/dev/null | grep -q "^${SESSION}$"; then
echo "Tilt session already exists: $SESSION"
else
zmx run "$SESSION" 'tilt up'
echo "Started tilt in zmx session: $SESSION"
fi
Critical: Never Restart for Code Changes
Tilt live-reloads automatically. Never suggest restarting tilt up for:
- Tiltfile edits
- Source code changes
- Kubernetes manifest updates
Restart only for: Tilt version upgrades, port/host changes, crashes, cluster context switches.
References
- TILTFILE_API.md - Tiltfile authoring
- CLI_REFERENCE.md - Complete CLI with JSON patterns
- https://docs.tilt.dev/
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★36 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
tilt reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Maya Liu· Dec 24, 2024
Keeps context tight: tilt is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Olivia Nasser· Dec 16, 2024
tilt has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Olivia Haddad· Dec 8, 2024
We added tilt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mia Gonzalez· Nov 27, 2024
Solid pick for teams standardizing on skills: tilt is focused, and the summary matches what you get after install.
- ★★★★★Piyush G· Nov 15, 2024
I recommend tilt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Olivia Ndlovu· Nov 7, 2024
tilt fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Valentina Park· Oct 26, 2024
We added tilt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mia Martinez· Oct 18, 2024
tilt has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Shikha Mishra· Oct 6, 2024
Useful defaults in tilt — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 36