Skip to content

feat(agents): add auggie adapter#130

Closed
yyovil wants to merge 1 commit into
agents/10-goosefrom
agents/11-auggie
Closed

feat(agents): add auggie adapter#130
yyovil wants to merge 1 commit into
agents/10-goosefrom
agents/11-auggie

Conversation

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Jun 6, 2026

Greptile Summary

Adds the auggie adapter package for driving Augment Code's auggie terminal agent in headless --print mode, registers it in Constructors(), and wires up the resolver test. The implementation follows the Tier C no-op pattern for hooks and session tracking, with intentional deferral to the user's Auggie config for all permission modes (Auggie has no blanket auto-approve flag).

  • auggie.go: new Plugin implementing adapters.Adapter + ports.Agent — binary discovery, launch command building, no-op GetAgentHooks/SessionInfo, and session resume via --resume <sessionId>.
  • registry/registry.go + wiring_test.go: single-line registration of auggie.New() and resolver smoke test for domain.HarnessAuggie.

Confidence Score: 5/5

Safe to merge; the adapter is a well-contained new package with no risk to existing adapters or the daemon boot path.

The change is additive: a new adapter package, a single registration line, and a single test assertion. All methods follow the established Tier C no-op pattern used by amp, aider, and crush. Context guards are present on every exported method. The documented design decisions (no permission flags, no hooks) are backed by comments explaining Auggie's CLI surface, and the test suite verifies the command shapes for every code path including context cancellation.

No files require special attention.

Important Files Changed

Filename Overview
backend/internal/adapters/agent/auggie/auggie.go New adapter implementing the full ports.Agent interface; binary discovery, launch/restore command building, and intentional no-ops for hooks and session info all follow established Tier C patterns correctly.
backend/internal/adapters/agent/auggie/auggie_test.go Thorough unit tests covering all public methods, context cancellation, and permission-mode flag suppression; consistent with test patterns in sibling adapters.
backend/internal/adapters/agent/registry/registry.go Single-line addition of auggie.New() to Constructors() in the correct position; no issues.
backend/internal/daemon/wiring_test.go One-line addition to the resolver smoke test asserting domain.HarnessAuggie resolves to the auggie adapter; correct and consistent with all other harness entries.

Reviews (2): Last reviewed commit: "feat(agents): add auggie adapter" | Re-trigger Greptile

Comment thread backend/internal/adapters/agent/auggie/auggie.go Outdated
Comment thread backend/internal/adapters/agent/auggie/auggie.go
Registers the auggie harness, stacked on the agent platform.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

2 participants