tilt-dev / tilt-dev/tilt

AI Agent support

Open
#6,567 10 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Description

Describe the Feature You Want

I'd like to connect the AI Agent in my editor to Tilt so the agent can trigger resources and see what happens while editing my project.

Two potential ways to do this would be:

  • tilt CLI commands to trigger resources and get their results, including the logged output
  • MCP support for the agent to directly interact with Tilt, in much the same way a human interacts with the web UI
Current Behavior

My agent can't trigger resources, so I either have to:

  • Trigger the resource myself and manually tell the agent what happened
  • Factor the resource's commands into a separate script and instruct the agent to run the script. Sometimes this is a little janky. Say triggered resource R has a dependency on resource D which in turn is triggered by edits to file F. If the agent edits F, it doesn't have any way to know if/when D has successfully completed so it can run the script for R.
Why Do You Want This?

I'm using TIlt in a large project and using an AI agent to perform some tasks within that project.

Additional context

I'm using Zed, but ideally the solution is portable to a variety of editors such as Cursor, Windsurf, etc.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests; start by reviewing Tilt's existing CLI resource controls and the web UI interactions that an agent would need to reproduce. Compare the proposed CLI and MCP approaches, using the dependency and completion workflow described in the issue. Done should let an editor agent trigger resources and inspect results, including logs and dependent-resource completion.

Written by the indexing model from the issue text.

Assessment

Domain
cli, developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.