Add experimental Auggie engine support#42314
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
🔍 PR Triage — §28395315609
Score breakdown: impact 25 + urgency 5 + quality 10
|
|
I ran the external Auggie smoke test in a temporary public repo. Repo: https://github.com/carlosflorencio/gh-aw-auggie Result: failure in What passed:
Failure:
This looks like the intended PR behavior is not wired through yet: exclude |
|
Hey This looks ready for maintainer review — tests are present, the description covers all the moving parts, and the diff is focused entirely on Auggie support. The
|
🤖 PR Triage — Run §28413530597
Notes: Draft (7.1h). Very large experimental feature: 288 files, +3213/-558. No CI yet. Defer until promoted from draft with CI results. Labels confirmed correct.
|
🤖 PR Triage — Run §28445959231
Score breakdown: Impact 22/50 · Urgency 12/30 · Quality 9/20 Experimental Auggie engine support (3213+/558−, 288 files) — large high-risk DRAFT, no CI. Part of
|
🤖 PR Triage
Score breakdown: Impact 25/50 · Urgency 8/30 · Quality 10/20 Rationale: DRAFT. Experimental Auggie engine support (+3213/-558). Large change, no CI. Carried over from prior triage runs. Defer until draft is ready and CI is green.
|
🤖 PR Triage — §28486872548
Score breakdown: Impact 25/50 · Urgency 5/30 · Quality 8/20 Batch: Rationale: Very large experimental Auggie engine addition (+3213/-558, 288 files). Draft, no reviews. High risk due to scope. Defer until experimental status is resolved and PR is ready for review. Labels applied:
|
🤖 PR Triage (carried over)
Score breakdown: Impact 25 + Urgency 5 + Quality 8 Rationale: Experimental Auggie engine integration — still in draft, no CI. Low urgency. Carry alongside #42100 in the experimental batch until author marks ready.
|
This adds Augment Code's Auggie CLI as a new experimental engine so workflows can use
engine: auggiealongside the existing agentic engines. It wires Auggie through compilation, runtime metadata, docs, schema validation, and smoke coverage usingAUGMENT_SESSION_AUTHfor authentication.Engine registration and defaults
auggieengine ID, default version pin (0.29.0), model env vars, engine option metadata, and built-in engine definition.Runtime implementation
AuggieEnginewith experimental metadata and Auggie-specific capabilities:.augment/@augmentcode/auggie, validateAUGMENT_SESSION_AUTH, render standard JSON MCP config, and emit Auggie execution steps with:--print --quiet--model--mcp-configFirewall and domain handling
AUGMENT_SESSION_AUTHfrom forwarded firewall env while still making it available to the agent process.Schema, docs, and UX
auggie.Smoke workflow and generated artifacts
smoke-auggie.mdand compile it to a lockfile..augment/manifest protection and engine catalog state are reflected consistently.Example workflow:
At execution time this compiles down to an Auggie invocation shaped like: