---
schema_version: 1
route: /t/tilt.md
tool: "tilt"
---

# sincecutoff.com /t/tilt — Tilt

- name: Tilt
- kind: cli
- children: none
- homepage: <https://github.com/tilt-dev/tilt>

Changes to the tools coding agents drive, since a model's training cutoff, each linked to its first-party source. Check installed versions and limitations before acting; a cutoff date does not establish what a model knows.
Original editorial content: [Apache 2.0](https://sincecutoff.com/v1/data-license.txt), by [0xPatrick](https://0xpatrick.dev). Preserve applicable license and [NOTICE](https://sincecutoff.com/notice.txt) attribution when redistributing. Third-party source text and examples retain their own rights. [License scope and attribution](https://sincecutoff.com/v1/license.json).
To stay current, read the changes feed: [`/v1/changes.md?tool=tilt`](https://sincecutoff.com/v1/changes.md?tool=tilt) (or `.json`), adding `since=YYYY-MM-DD` for your training cutoff. Entries for registered children are included; the registry itself is `/v1/tools.json`. How to page and save your place: [llms.txt](https://sincecutoff.com/llms.txt).

### Tilt live_update adds initial_sync for pre-built images (2026-04-30)
- slug: tilt-live-update-adds-initial-sync-for-pre-built-images-2ac61cd1a063
- score: 0.97

How to use it:

For a pre-built image, add `initial_sync()` first in `live_update` to upload files from its `sync` paths when Tilt first observes a running container and after restarts. Then define `sync` steps and optional `run` triggers; during initial sync, untriggered `run` steps execute and triggered ones execute only when synced files match.

Examples:

```
live_update=[
    initial_sync(),
    sync('./src', '/app/src'),
    run('npm install', trigger=['./src/package.json']),
]
```

- why_it_matters: Use a pre-built image in a Tiltfile and sync local files into its container on start or restart.
- sources: <https://github.com/tilt-dev/tilt/releases/tag/v0.37.3>, <https://github.com/tilt-dev/tilt/pull/6737>, <https://docs.tilt.dev/live_update_reference.html>
- gotchas: "Version: v0.37.3"; "initial_sync(): Must be first if provided. Takes no arguments; uploads files from `sync` paths when Tilt first observes a running container and whenever it restarts."; "sync(local_path, remote_path) (required): Local file or directory path and destination path in the container."; "run(cmd, trigger) (required): `cmd` runs in the container. Optional `trigger` is a filepath or list of filepaths; the command runs if synced files match. Without a trigger, it runs after initial sync completes."; "live_update (required): List of live update steps supplied when building or deploying an image; `initial_sync` precedes `sync`, which precedes `run`."; "Prerequisite: The image or deploy must be sufficient to start a running container without relying on synced files or `run` commands."; "Prerequisite: `sync` paths must be within the watched build context (or custom build dependencies)."; "`initial_sync()` must be first in the list."; "No compression; tested with gzip, but CPU overhead exceeded network savings for typical workloads (~20k files, ~90MB in under 20s to remote EKS)."; "No changes to existing `live_update` behavior."; "Docs conflict: The release note describes `initial_sync(ignore=..., dockerignore=...)`, but the current official reference says `initial_sync()` takes no arguments and describes exclusions through the image or custom deploy's file-watching controls. Do not use the release-note parameters based on this page. The official reference's current content may be newer than v0.37.3."

### tilt alpha tree-view displays dependency resources (2026-03-04)
- slug: tilt-alpha-tree-view-displays-dependency-resources-9d7ed8818e36
- score: 0.97

How to use it:

When you need to find resources blocking readiness, run `tilt alpha tree-view --blockers` to show blocked resources and their root blockers. The tree is organized by dependencies from the root Tiltfile; use `--dedupe` to show repeated subtrees only once.

Examples:

```
tilt alpha tree-view --blockers
```

```
tilt alpha tree-view --dedupe
```

- why_it_matters: Inspect a Tilt environment's dependency tree to find resources blocking readiness.
- sources: <https://github.com/tilt-dev/tilt/releases/tag/v0.37.0>, <https://github.com/tilt-dev/tilt/pull/6678>, <https://docs.tilt.dev/cli/tilt_alpha_tree-view.html>
- gotchas: "Version: v0.37.0"; "Availability: alpha"; "--blockers: Show only blocked resources and their root blockers."; "--dedupe: Deduplicate resources with multiple parents; show subtrees only once with annotations."; "The tree starts from the root Tiltfile."

### Tilt update_settings adds k8s_server_side_apply (2026-03-04)
- slug: tilt-update-settings-adds-k8s-server-side-apply-c8fcf2db6855
- score: 0.96

How to use it:

To control server-side apply for Kubernetes updates, set `k8s_server_side_apply` in the Tiltfile’s `update_settings` call to `"true"`, `"false"`, or `"auto"`.

Examples:

```
update_settings(k8s_server_side_apply="true")
```

- why_it_matters: Configure whether Tilt uses Kubernetes server-side apply for resources in an environment.
- sources: <https://github.com/tilt-dev/tilt/releases/tag/v0.37.0>, <https://github.com/tilt-dev/tilt/pull/6680>, <https://docs.tilt.dev/api.html#api.update_settings>
- gotchas: "Version: v0.37.0"; "k8s_server_side_apply: String controlling whether Kubernetes applies use server-side apply. Accepted values are `true`, `false`, and `auto`; default is `auto`."; "The option accepts only the stated values: `\"true\"`, `\"false\"`, or `\"auto\"`."

### tilt logs adds time, tail, and JSON output flags (2026-01-20)
- slug: tilt-logs-adds-time-tail-and-json-output-flags-e950e36a23d5
- score: 0.97

How to use it:

When debugging an application running through Tilt, use `tilt logs` to inspect its logs; add `--since=<duration>` for recent logs, `--tail=<count>` to limit lines, or `--json` for JSON Lines output.

Examples:

```
tilt logs --since=5m <resource>
```

```
tilt logs --tail=100 <resource>
```

```
tilt logs --json <resource>
```

- why_it_matters: Inspect Tilt logs while debugging an application running through Tilt.
- sources: <https://github.com/tilt-dev/tilt/releases/tag/v0.36.1>, <https://docs.tilt.dev/cli/tilt_logs.html>
- gotchas: "Version: v0.36.1"; "--since <duration>: Show logs only from the specified duration ago, such as `5m`, `1h`, or `30s`."; "--tail <int>: Number of lines to show from the end; `-1` means all lines and is the default."; "--json: Output logs in JSON Lines format."; "Prerequisite: A Tilt instance must be running; `tilt logs` connects to localhost:10350 by default."
