[Lyther]

Summary

Antigravity + Kilo Code agent support

• Add Google Antigravity integration: project-scoped rules via .agents/rules/ (confirmed against Antigravity 1.107.0)
• Add Kilo Code rules support (project-scoped only)
• Real-env testing confirmed Antigravity is a Windsurf/Codeium fork with NO hooks.json — dead hook code removed

Vector	Command	Mechanism
Cascade AI rules	rtk init --agent antigravity	.agents/rules/antigravity-rtk-rules.md
Claude Code hooks	rtk init -g	~/.claude/settings.json PreToolUse (works inside Antigravity)

GCP filters

• gsutil.toml, bq.toml, expand gcloud.toml with 7 subcommand filters
• pip-install.toml, expand uv-sync.toml with init/add/lock, conda.toml

Wire 21 orphaned TOML filters

gcc, gradle, jq, oxlint, basedpyright, jira, jj, just, mise, nx,
ollama, skopeo, spring-boot, ssh, stat, task, turbo, ty, xcodebuild, yadm
(all had TOML filters but no rules.rs entries — dead code until now)

New ecosystem TOML filters

File	Filters	Savings	Tests	Closes
bun.toml	install, test, build	60-70%	3	#832
yarn.toml	install, test	60-80%	3	#902
bazel.toml	build, test, query	70-75%	3	#1061
flutter.toml	build, analyze, test, pub	90-100%	5	#1098
eza.toml	ls replacement	65%	1	#1030

Other

• Add podman as docker alias (feat: support podman commands along with docker #1034)
• Add python -m pip to pip rewrite rule
• Fix let-else lints in hook_check.rs, duplicate remove_var in trust.rs
• Fix gradle rewrite regex

Closes #832 #902 #1030 #1034 #1061 #1098

Token Savings (measured on rtk repo)

Command	Raw	Filtered	Savings
cargo test	5,568	9	99.8%
cargo clippy	457	46	89.9%
ls -la src/	101	10	90.1%
git status	59	9	84.7%
git log -20	1,162	696	40.1%
Session total	9,985	2,606	73.9%

Stats

• Filter count: 58 → 86 (+28)
• Rule count: 72 → 97 (+25)
• 18/18 new rewrite tests pass
• Startup: <1ms | Binary: 5.8MB | RSS: 5.9MB

Test plan

• cargo test — 1368 passed, 0 failed
• cargo clippy --all-targets — zero warnings from changed files
• All 86 TOML filters have inline tests
• Rewrite verified: bun, yarn, bazel, flutter, dart, eza, podman, gcc, gradle, jq, just, oxlint, turbo, xcodebuild, conda, python3 -m pip
• E2E: rtk init --agent antigravity verified against local Antigravity 1.107.0
• E2E: gcloud/gsutil/bq rewrite works
• Performance unchanged: <1ms startup, 5.8MB binary, 5.9MB RSS

[CLAassistant]

All committers have signed the CLA.

[aeppling]

Hello, Antigravity and KiloCode support already on develop branch and will be in next release.

But new gcp filters are welcome !

Thanks for contributing

[Lyther]

The upstream develop branch already has d0a3797 which added basic project-scoped rules for Antigravity and Kilo Code (by @Yosoyepa). This patch builds on that foundation in three layers:

1. Antigravity hardening — Tested against a local Antigravity 1.107.0 install and discovered it's a Windsurf/Codeium fork, not Cursor. The original commit assumed a hooks.json protocol that doesn't exist. We added the global hook code, validated it was dead, then removed it — leaving only the confirmed-working .agents/rules/ path plus guidance to use rtk init -g (Claude Code hooks) for transparent rewriting.

2. GCP ecosystem — Expanded gcloud.toml with 7 subcommand filters, added gsutil.toml, bq.toml, pip-install.toml, conda.toml, and expanded uv-sync.toml to cover init/add/lock. These are the noisy commands Antigravity's Cascade actually runs.

3. Broad filter coverage — Wired 21 existing TOML filters that had no rules.rs entries (completely unreachable dead code), and added 5 new ecosystem filters (bun, yarn, bazel, flutter/dart, eza) plus podman as a docker alias. Closes #832 #902 #1030 #1034 #1061 #1098.

Net: 58 → 86 TOML filters, 72 → 97 rules, 73.9% token savings measured on real sessions.

[adam-azarchs]

Suggested change

	match_command = "^bazel\\s+query\\b"
	match_command = "^bazel(isk)?\\s+[ca]?query\\b"

Also all of these should probably be made to handle startup flags between bazel and the verb.

[adam-azarchs]

I am not sure this test accurately reflects the reality of whether it's going to work correctly in production; as #1061 points out, most of bazel's output is stderr, not stdout. You need to add filter_stderr:

rtk/src/core/toml_filter.rs

Lines 105 to 108 in 4c278d1

	/// When true, stderr is captured and merged with stdout before filtering.
	/// Use for tools like liquibase that emit banners/logs to stderr.
	#[serde(default)]
	filter_stderr: bool,

[adam-azarchs]

strip_ansi is going to be doing the wrong thing here. We do want to strip out colors, but bazel makes extensive use of ansi escape sequences to overwrite progress lines. It's possible that you can catch all such lines with regexes, but it would be more reliable to just remove anything that gets overridden, before proceeding to regex-match remaining lines that are not of interest. rtk arguably should just do that for everything, before it gets to the point of these regex matchers.

[KuSh]

Heads-up: #988 adds native bun/deno command support (Rust filters, not TOML) and is close to landing. It overlaps two things here, and only two:

• src/filters/bun.toml — superseded. feat(bun,deno): add Bun and Deno runtime support #988 filters bun install/add/remove, test, pm ls natively and deliberately passes build/run through.
• the discover rule ^(bun|bunx)\s+(test|run|install|build|add)\b → rtk bun — conflicts with feat(bun,deno): add Bun and Deno runtime support #988's own bun and bunx rules. classify_command takes the first match in RULES, so with both present the winner depends on ordering.

Not asking you to close this PR — the other 21 files (Antigravity/Kilo Code hooks, the GCP filters, bazel/conda/eza/flutter/pip-install/uv-sync/yarn, the toml_filter.rs changes) are independent and unaffected. Dropping just those two pieces on your next rebase should be enough.

One thing worth knowing if you'd rather keep a TOML path for bun: bun-install strips ^\s*\+, which removes bun's + package@version lines — those are the substantive output of an install, so the filter as written discards the part worth keeping. #988 keeps them and strips the version header and resolution lines instead, measured at ~70% on a real capture.

This PR is currently marked conflicting, so it needs a rebase regardless.

[KuSh]

Antigravity and Kilo Code support landed on develop with commit d0a3797 (2026-04-08), and #988 (merged 2026-09-03) added native Rust filters for bun, so bun.toml and the bun discover rule here are no longer needed. Most of the orphaned filters you wired also rewrite on develop now. What develop still lacks from this branch is the TOML filters and rewrite rules for yarn, bazel, flutter/dart, eza, gsutil, bq, conda and pip-install, the gcloud subcommand expansion, uv-sync init/add/lock, podman as a docker alias, the python -m pip rewrite, and the rewrite wiring for mise and ollama. Could you rebase onto current develop and narrow the PR to those parts? It currently conflicts with develop, so expect to resolve conflicts in src/discover/rules.rs and the init code, and to drop the release and version files. Thanks for all the work on these filters.