wbmeet

Augment Code in VS Code installieren: Anmeldung, Completions und Agent

Augment-Erweiterung installieren, anmelden, Repo synchronisieren, dann Inline-Vorschläge oder eine prüfbare Agent-Änderung.

In der ersten Stunde mit Augment Code in VS Code scheitert es selten am Prompt, sondern an Extension augment.vscode-augment, Browser-Anmeldung oder laufender Workspace-Indexierung. Marketplace installieren, mit Google, Microsoft oder E-Mail-Einmalcode anmelden, dann Inline-Vervollständigungen (je nach Plan) oder eine prüfbare Agent-Änderung testen.

Die Suchanfrage lautet Augment Code in VS Code installieren und nutzen. Folgt docs.augmentcode.com. Kein Meeting-Produkt dieser Site. Kurzes Diff-Gespräch: wbmeet, Raum erstellen und beitreten.

Extension installierenAnmelden & syncCompletions & Agent

What Augment does in VS Code

Augment Code is an AI coding platform for large codebases: its Context Engine indexes your workspace and powers Chat, Agent (multi-file edits, terminal, MCP), and IDE-native inline completions. Extension id: augment.vscode-augment. Use a current VS Code build; pre-release builds exist but may be unstable.

Tab accept
Inline completions (Enterprise)
Agent mode
Multi-file Agent & terminal
.gitignore
Index ignore rules

Install, sign in, sync the workspace

  1. 1

    Install from the VS Code Marketplace

    Open VS Code, Cmd+Shift+X / Ctrl+Shift+X, search Augment, confirm augment.vscode-augment, Install. For pre-release, use Switch to Pre-Release Version on the installed extension.

  2. 2

    Open the Augment panel and Sign In

    Click the Augment icon in the Activity Bar or use the official shortcut, then Sign In. Authenticate in the browser with Google, Microsoft, or an email one-time code; accept terms on first login. The status bar icon shows signed-in state when it works.

  3. 3

    Sync (index) the workspace

    On a new repo you will see Sync your workspace. Augment uploads files (respecting .gitignore and .augmentignore) to build codebase awareness. Check progress in Workspace Context; put secrets paths in .augmentignore.

  4. 4

    Try inline completions (if your plan supports them)

    Type in source files; gray suggestions accept with Tab, dismiss with Esc. Toggle automatic completions from the Augment panel overflow menu; settings include augment.completions.enableAutomaticCompletions. Non-Enterprise accounts may lack Completions after 2026-03-31 per official docs.

Agent mode: cross-file edits you can review

  1. 1

    Choose Agent in the mode dropdown

    In the Augment panel input, pick Agent (there is also Agent Auto, which acts more independently—skip Auto for the first hour). Choose a model for the workspace from the model dropdown.

  2. 2

    Attach context and submit a task

    Default context includes the workspace and open file. Attach files, folders, or images. Start read-only or small: “Where is this module’s entry?” or “Add a unit test for one helper; show the diff first.” Use Enhance Prompt to align with repo conventions.

  3. 3

    Review diffs, checkpoints, and Stop

    Expand each step for file diffs, terminal output, and MCP calls. Checkpoints let you roll back. Default Agent pauses before terminal commands until you click play; use Stop to interrupt. Quick Ask Mode is read-only—good for reconnaissance.

# First hour · Augment Code · VS Code · 2026-09
# Extensions → Augment (augment.vscode-augment)
# Panel → Sign In → Google / Microsoft / email code
# Sync workspace · .augmentignore for secrets
# Tab completions (Enterprise per 2026-03-31 policy)
# Agent → small task → review diff · checkpoint

Completions, Agent, and Chat

FeatureGood forFirst-hour note
Inline completionsTyping continuationsEnterprise only after 2026-03-31
ChatExplain & planRead-only warmup
AgentMulti-file features & testsApprove terminal steps
Agent AutoMore autonomous runsSkip Auto first hour
IndexingWhole-repo context.gitignore + .augmentignore
01

Still offline after login

Check pop-up blockers, terms acceptance, and VS Code’s external-link prompt. Sign Out from the command menu and sign in again.

02

No gray completions

Check overflow menu and augment.completions.* settings; confirm Enterprise plan (non-Enterprise may lose Completions after 2026-03-31).

03

Agent changed too much

Revert a checkpoint; shrink the task; use Quick Ask read-only; manually approve terminal steps.

Official path: install augment.vscode-augment → Sign In → Sync workspace → (Enterprise) Tab completions → Agent with a small task and reviewed diff. Trust docs.augmentcode.com and your account page.

Indexing uploads code
With Augment enabled, workspace files (minus ignore rules) sync to Augment’s cloud. Use .augmentignore for secrets; follow org policy.
Completions ≠ Agent
Completions are inline suggestions; Agent is multi-step execution. In mid-2026, non-Enterprise users should plan around Agent/Chat and indexing, not assume Tab completions.
Not a meeting-product guide
Only Augment’s first hour. Short whiteboard call: wbmeet and wann keine schwere Meeting-App.

Questions worth checking

Must I use Google or Microsoft?

Official sign-in supports Google, Microsoft, and email one-time codes via the browser portal, then returns you to VS Code.

Do personal plans still get completions?

Docs say Completions end for non-Enterprise plans on 2026-03-31; Enterprise remains supported. Use Chat/Agent if ghost text never appears.

Agent vs Chat?

Chat answers and suggests; Agent implements plans across files, runs the terminal, and uses MCP. Multi-file features and hands-off tasks belong in Agent.

Must the first task touch production?

No. Ask a read-only question first, then one reversible Agent change; read diffs and checkpoints before scaling up.

Kostenloses Meeting starten