Repository navigation
docs: add Auggie 1.x preview & migration guide - #176
augmentmoogi wants to merge 4 commits into
Conversation
How does this work?Specialized experts work independently on the same change. The dashboard gathers their latest evidence in one place; humans remain responsible for judgment and merge. 🤖 Expert roles
👤 Human role
|
|
👋 I've got this PR. |
| - **GitHub PR Reviews**: Preserved inline review comment reply relationships and threading. | ||
|
|
||
| #### `v1.2.0-prerelease.202610051436` | ||
| - **System Prompts**: Honored user-defined custom system prompts in session agent loops. |
There was a problem hiding this comment.
This is not customer facing, internal only
|
👀 Human review needed Justification
Reviewed commit d4f149c → Pair Review BriefingReviewed commit d4f149c |
| - **Snappier Terminal UI (Direct ANSI Engine)**: | ||
| In 0.x, the terminal interface could stutter or lag during fast token streaming or when printing large diffs. In 1.x, the rendering engine has been rewritten from scratch with a direct terminal renderer (`pi-tui`), delivering instant scrolling, smooth rendering, and zero redraw lag. | ||
| - **Native Editor Integration via ACP (Agent Client Protocol)**: | ||
| Auggie 1.x includes native support for ACP, enabling you to use Auggie as your coding agent directly inside editors like VS Code and Zed. Run `auggie acp` to start the protocol bridge and connect your favorite editor seamlessly. |
There was a problem hiding this comment.
auggie acp does not start the protocol bridge: parseArgs treats the bare acp argument as prompt text, leaving ACP mode disabled. An editor launched with this command cannot establish its ACP connection because it receives the normal CLI behavior instead of the protocol server.
Severity: medium
🤖 Was this useful? React with 👍 or 👎
| - **Tool Permissions**: Restrict or require user confirmation for specific tools via `/permissions` or `.augment/settings.json`. | ||
|
|
||
| ### Hook Tool Names Changed (With Temporary Backward Compatibility) | ||
| Tool names have been standardized to short, canonical verbs across Auggie 1.x. If you have custom hooks configured in `.augment/hooks.json` or plugin settings, note the following canonical tool name updates: |
There was a problem hiding this comment.
.augment/hooks.json is not a project hook configuration source in 1.x: loadHooksConfigWithDiagnostics reads the hooks property from scoped settings files, while standalone hooks/hooks.json files are loaded only for plugins. Readers who configure or migrate their project hooks at the documented path will find that none of those hooks execute.
Severity: medium
🤖 Was this useful? React with 👍 or 👎
| | `find` | `file-search`, `file_search`, `find-by-name` | Find files matching glob patterns | | ||
| | `bash` | `launch-process`, `launch_process`, `shell` | Run shell commands | | ||
|
|
||
| > **Note on Compatibility**: Temporary backward compatibility is provided in 1.x. Existing hook matchers and permission rules specifying legacy tool names (e.g. `matcher: "str-replace-editor"`) will continue to trigger for the canonical 1.x tools during the preview period. However, you should update your configuration to use the canonical names. |
There was a problem hiding this comment.
The listed aliases are not all supported by permission rules: names such as read-file and launch_process are hook-only aliases, whereas isRuleMatch checks the narrower shared getToolNameAliases set. Relying on this compatibility assurance can leave a deny rule ineffective for the canonical tool even though its corresponding hook still runs.
Severity: medium
🤖 Was this useful? React with 👍 or 👎
| - **Improved TUI Navigation & Unified Key Mapping**: | ||
| Navigation across menus and popovers is now unified: | ||
| - **Type-to-Filter**: All selectors (model picker, worktree selector, settings) support typing directly to filter results. | ||
| - **Consistent Keybindings**: Standardized navigation across the interface (`j`/`k` or arrow keys, readline shortcuts like `Ctrl+A`/`Ctrl+E`, `Escape` to step back or dismiss). |
There was a problem hiding this comment.
j and k are not default selector-navigation bindings: tui.select.up/down use arrow keys, and the model and worktree selectors pass those letters to their search inputs. Following this shortcut guidance filters the available choices instead of moving the selection.
Severity: low
🤖 Was this useful? React with 👍 or 👎
| - **In-Session Inspectors (`/rules`, `/hotkeys`)**: | ||
| Inspect active configuration layers in real time: `/rules` to view loaded system and workspace rules, and `/hotkeys` for a complete keyboard shortcut reference. | ||
| - **Configurable Themes**: | ||
| Settings in `.augment/settings.json` now support custom color themes via `theme` (`"dark"`, `"light"`, or custom theme files) and persistent reasoning budgets via `defaultThinkingLevel`. |
There was a problem hiding this comment.
defaultThinkingLevel is not honored when starting a fresh session with an Augment-backed model: createAgentSession reads its model-specific reasoningEffortPreferences or uses the model default instead. Users who configure the advertised setting for their normal Augment sessions therefore will not get the persistent reasoning effort described here.
Severity: medium
🤖 Was this useful? React with 👍 or 👎
|
|
||
| ## 2. Feature Highlights (What’s New in 1.x) | ||
|
|
||
| > *Note: These are curated highlights of user-facing capabilities introduced in 1.x that were not available in 0.x. For release-by-release details, see the [Changelog](#5-detailed-changelog) below.* |
There was a problem hiding this comment.
Several following highlights were already available in 0.x: this repository's CHANGELOG.md records ACP as fully released in 0.9.0, /rules improvements in 0.5.6, and interactive permission editing in 0.5.1. Calling all of these capabilities unavailable in 0.x misrepresents the migration benefits and implies users need a preview upgrade for existing stable features.
Severity: low
🤖 Was this useful? React with 👍 or 👎
Problem
Users need clear documentation explaining the upcoming Auggie 1.x release, distribution tags, breaking changes, and migration details.
Linear ticket: AGT-1142
Solution
docs/1.x-preview-guide.mdcovering distribution channels (latest,preview,daemon), feature highlights, breaking changes, WIP roadmap, and tag changelog.README.md.Pull Request opened by Augment Code | View session