Skip to content

馃摑 Deprecate context --agent mode - #365

Merged
Robdel12 merged 3 commits into
mainfrom
rd/deprecate-agent-context
Sep 28, 2026
Merged

Robdel12 merged 3 commits into
mainfrom
rd/deprecate-agent-context

Conversation

@Robdel12

@Robdel12 Robdel12 commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Why

Vizzly's schema-driven API gives agents a flexible way to fetch focused cloud review context. The older context build --agent and context comparison --agent formats duplicate that path and can return oversized responses, so new workflows should move to the API.

Approach

Keep both legacy formats working with a deprecation warning until their planned removal in v0.38.0. Make the bundled skill and setup guidance API-first without mentioning the sunset, so agents won't need another skill update when the flags are removed. CLI help and user docs explain the deprecation. Local TDD workflows keep their existing JSON context commands.

The optional reminder for repos with an outdated installed skill is tracked separately in #366.

Evidence

The command coverage checks the warning, JSON output, follow-up commands, and generated setup guidance. The legacy formats remain available during the deprecation period.

Keep the compact context path working through v0.37.x while directing new cloud review workflows to schema discovery. This keeps generated commands and setup guidance aligned with the public API.
Leave the installed skill and init guidance on the existing compact workflow through v0.37.x. The CLI warns when users invoke the old flags, and the next-step output points new cloud work to schema discovery.
Update the installed skill and init guidance to use schema discovery for cloud reviews. Keep the removal date in CLI warnings and human docs, not in the skill, so the instructions remain current when the old flags are removed.
@Robdel12
Robdel12 merged commit ae96527 into main Sep 28, 2026
27 of 30 checks passed
@Robdel12
Robdel12 deleted the rd/deprecate-agent-context branch September 28, 2026 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant