# \[vs-code-extension\] How to view background task logs?

**URL:** <https://discuss.ai.google.dev/t/vs-code-extension-how-to-view-background-task-logs/186146>\
**Category:** Google Antigravity\
**Tags:** feature-request, help-request\
**Created:** [September 30, 2026, 1:39pm UTC](https://discuss.ai.google.dev/t/vs-code-extension-how-to-view-background-task-logs/186146 "2026-09-30T13:39:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfrantzius](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/jfrantzius/32/154135_2.png) [@jfrantzius](https://discuss.ai.google.dev/u/jfrantzius)\
**Post date:** [September 30, 2026, 1:39pm UTC](https://discuss.ai.google.dev/t/vs-code-extension-how-to-view-background-task-logs/186146/1 "2026-09-30T13:39:13Z")

</div>

Hi,

when using the `google.google-antigravity` VS code extension `1.6.0`, there seems to be no way of viewing the output of any background tasks that are started by the agent. The “Auxiliary Pane” does list the tasks, but neither allows access to their output.

Is this maybe hidden somewhere in the UI, or is this a missing feature? When running long builds etc. it would be helpful to see the logs, also to e.g. see exact build failures in context.

Thanks for any hints + hi to the community 🙂

---

<div class="post-metadata">

**Author:** ![Ambati\_Rajendra](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/ambati_rajendra/32/31584_2.png) [@Ambati\_Rajendra](https://discuss.ai.google.dev/u/Ambati_Rajendra)\
**Post date:** [September 30, 2026, 7:37pm UTC](https://discuss.ai.google.dev/t/vs-code-extension-how-to-view-background-task-logs/186146/2 "2026-09-30T19:37:58Z")

</div>

Hi @jfrantzius,

Could you please a few details:

- The exact reproduction steps to reproduce this issue?
- If it is possible could you please provide a screenshot of that particular issue?

---

<div class="post-metadata">

**Author:** ![dllhell](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/dllhell/32/156437_2.png) [@dllhell](https://discuss.ai.google.dev/u/dllhell)\
**Post date:** [September 30, 2026, 10:05pm UTC](https://discuss.ai.google.dev/t/vs-code-extension-how-to-view-background-task-logs/186146/3 "2026-09-30T22:05:39Z")

</div>

Hi @jfrantzius,

To answer your question directly: **Yes, this is currently a missing UI feature in the `google.google-antigravity` VS Code extension (1.6.0).**

In version 1.6.0, the Auxiliary Pane registers active background tasks, but the extension UI does not yet expose an **“Open Task Output”** or **“Attach Terminal”** context action. This occurs because the extension executes background tasks as detached worker processes with standard streams redirected to on-disk log buffers rather than binding them to an interactive VS Code pseudo-terminal (`vscode.window.createTerminal`).

However, the complete, unbuffered stdout and stderr logs **are physically written to disk in real time**. You can inspect or live-stream them right now using these workarounds:

* * *

### 1. Live-Stream Logs in VS Code Terminal (Quickest Workaround)

Open your integrated VS Code terminal (`Ctrl+` `/`Cmd+` `) and tail the active task logs directly:

- **Linux / macOS** :

```bash
tail -f ~/.gemini/antigravity/brain/*/.system_generated/tasks/*.log

```

- **Windows (PowerShell)**:

```powershell
Get-Content -Path "$env:USERPROFILE\.gemini\antigravity\brain\*\.system_generated\tasks\*.log" -Tail 50 -Wait

```

Every background task is assigned a dedicated `task-<id>.log` containing the unbuffered compiler output, exact stack traces, and exit codes.

* * *

### 2. Open the File Directly in the VS Code Editor

If you want to search (`Ctrl+F` / `Cmd+F`) through build failures:

1. Press `Ctrl+O` / `Cmd+O` (File: Open File).
2. Navigate to:
  - **Linux/macOS** : `~/.gemini/antigravity/brain/<session-uuid>/.system_generated/tasks/`
  - **Windows** : `%USERPROFILE%\.gemini\antigravity\brain\<session-uuid>\.system_generated\tasks\`

3. Open the corresponding `task-<id>.log`. VS Code will auto-refresh as new lines are appended.

* * *

### 3. Prompt the Agent in Chat

The agent’s internal `manage_task` tool natively resolves the exact log file URI and status. You can simply ask in chat:

> _“What is the current status and output of the active background task? Tail the last 30 lines of its log.”_

The agent can view the task log directly and diagnose the exact compiler/build errors in context.

* * *

### Feedback for the Extension Team

What would complete the Auxiliary Pane experience in an upcoming release is a simple context action:

- Right-click task in Auxiliary Pane → **“View Live Output”** (opening `task-<id>.log` in an editor tab with auto-tail enabled), or an inline terminal lens.

Hopefully this lets you monitor your long builds and catch failures without waiting blindly.