bug: /statusline slash command does not open the status line configuration interface

[vitorlee]

Description

When running the Antigravity/Gemini CLI in interactive mode and entering the /statusline slash command, the terminal does not display any configuration interface or settings menu for the status bar. The prompt simply accepts the command without any feedback or visual changes.

Steps to Reproduce

1. Launch the Antigravity CLI in interactive mode (gemini or antigravity).
2. Type /statusline at the prompt and press Enter.
3. Observe that no configuration interface appears.

Expected Behavior

An interactive interface or prompt menu should open to allow the user to select which metadata fields (such as Model, CWD, Token Usage, State) to show or hide in the status bar.

Actual Behavior

Nothing happens. The cursor goes to the next line, and no configuration options are displayed.

Environment Details

• CLI Tool: Antigravity CLI (transitioned from Gemini CLI)
• OS Version: macOS (Darwin)
• Shell: zsh

[weby-homelab]

For anyone struggling to get the custom status line (or window title) working in Antigravity CLI, here is a complete guide and a fix.

Why /statusline doesn't open a UI

The /statusline slash command inside the TUI is designed to be interactive for toggling, but it doesn't open a configuration menu. By default, the CLI displays a minimal status line (? for shortcuts / esc to cancel). To get the rich status line with context bar, git branch, subagents, and tasks, you must configure a custom status line.

Manual Configuration

Add the statusLine (and/or title) blocks to your settings.json pointing to the scripts:

Settings File Locations:

• Linux: ~/.gemini/antigravity-cli/settings.json
• macOS: ~/Library/Application Support/antigravity-cli/settings.json
• Windows: %\APPDATA%\antigravity-cli\settings.json

JSON Structure:

{
  "statusLine": {
    "command": "/absolute/path/to/statusline.sh",
    "enabled": true
  },
  "title": {
    "command": "/absolute/path/to/title.sh",
    "enabled": true
  }
}

Note: The command path MUST be absolute. Relative paths or ~ home expansion will not work.

---

Easy Automated Setup (PR #196)

I've submitted Pull Request #196 (#196) which adds automated setup scripts to the repository:

# Automatically sets up the custom statusline:
bash examples/statusline/setup.sh

# Automatically sets up the dynamic terminal window title:
bash examples/title/setup.sh

These scripts automatically detect your OS, copy the script files to your global config directory, and update your settings.json with the correct absolute path.

---

Out-of-the-box Installation (Community Fork)

If you want the custom statusline and title configured and enabled by default right after installation, you can install the CLI from the community fork weby-homelab/antigravity-cli:

curl -fsSL https://raw.githubusercontent.com/weby-homelab/antigravity-cli/main/install.sh | bash

Our fork's installer handles copying the statusline and title scripts and enabling them in your settings automatically.

[Dragon1573]

Hi, 👋🏼

I'm currently running agy.exe on a Windows instance. It seems the provided statusline.sh only valid for those users on Linux or macOS with `Bash available.

I tried to migrate statusline.sh to statusline.ps1 for my pwsh.exe environment via Antigravity CLI + Gemini 3 Flash itself. But I failed to achieve as the script entirely ruined the status line.

Could official team provide scripts for Windows PowerShell (aka. powershell.exe), PowerShell Core (aka. pwsh.exe), Windows Command Prompt (aka. cmd.exe), Fish Shell (aka. fish) and other shell environments?

---

Instead of asking users to specify shell scripts on their own, I would recommend introducing JSON / YAML / TOML configuration file to configure segments of information - like what Oh My Posh is doing.

[weby-homelab]

Hi @Dragon1573,

We hear you! Running Bash scripts on Windows without a proper Unix environment is indeed a friction point, and translating complex ANSI-colored stream manipulation to PowerShell manually can be tricky.

To solve this, I've updated Pull Request #206 (#206) to include native example scripts for Windows, Fish, and a cross-platform Node.js version.

Here are the new additions in the examples/statusline/ and examples/title/ folders:

1. PowerShell (statusline.ps1 / title.ps1): Native scripts that run under Windows PowerShell (aka. powershell.exe) and PowerShell Core (aka. pwsh.exe). They have zero external dependencies (no jq required), using the built-in ConvertFrom-Json to parse standard input.
2. Node.js (statusline.js / title.js): A cross-platform vanilla Node.js implementation with zero external dependencies that works out-of-the-box on Windows, Linux, and macOS.
3. Fish Shell (statusline.fish / title.fish): Native fish scripts leveraging fish built-ins for color and math (jq required).

Configuration Examples for Windows / Fish:

PowerShell (Windows / pwsh):

{
  "statusLine": {
    "command": "powershell.exe -ExecutionPolicy Bypass -File C:\\path\\to\\statusline.ps1",
    "enabled": true
  },
  "title": {
    "command": "powershell.exe -ExecutionPolicy Bypass -File C:\\path\\to\\title.ps1",
    "enabled": true
  }
}

Node.js (Cross-platform):

{
  "statusLine": {
    "command": "node C:\\path\\to\\statusline.js",
    "enabled": true
  }
}

Fish Shell:

{
  "statusLine": {
    "command": "/absolute/path/to/statusline.fish",
    "enabled": true
  }
}

---

Regarding a Structured Config Format (like Oh My Posh)

This is an excellent suggestion! While external scripts offer 100% flexibility for custom logic (e.g. executing local API calls, fetching hardware metrics, or querying external APIs directly in the status line), they do introduce platform-specific complexity. A declarative JSON/YAML segment configuration would drastically simplify the basic setup. I will capture this in a separate feature request issue so the team can design a structured layout schema.

Let us know if the new PowerShell or Node.js scripts solve it for you!

[Dragon1573]

The provided script for PowerShell Core is perfect. ❤️

However, it still unable to display as expected at the bottom of Antigravity CLI. Should I place the script to somewhere else? Is ~/.gemini/antigravity-cli/ itself a "protected zone" so Antigravity CLI cannot load executable scripts in it?

PixPin_2026-05-29_11-38-08_1.mp4

[weby-homelab]

Hi @Dragon1573,

Glad to hear the PowerShell Core script is working perfectly on its own! ❤️

To answer your question: No, ~/.gemini/antigravity-cli/ is not a "protected zone." The CLI is fully capable of running scripts from that directory.

However, there are a few common Windows-specific and CLI-specific friction points that can prevent the status line from rendering. Here is how you can troubleshoot and fix it:

1. The ~ Path Expansion Issue (Most Likely)

When you run a command via settings.json, the Go-compiled agy binary spawns the subprocess directly. It does not expand the ~ character (which is a shell-specific shorthand).

• The Problem: If your settings.json contains ~/.gemini/..., the OS will look for a literal directory named ~ on your C: drive and fail.
• The Fix: Replace ~ with the full absolute path to your home directory, e.g., C:/Users/YourUsername/.gemini/antigravity-cli/....

2. JSON Backslash Escaping

Windows paths use backslashes (\), which are escape characters in JSON.

• The Problem: If you configure the path with single backslashes (e.g., C:\Users\Name), the JSON parser will fail to parse settings.json (as \U is treated as a malformed Unicode escape). If the JSON is invalid, the CLI falls back to defaults silently.
• The Fix: You must either double-escape the backslashes (C:\\Users\\...) or use forward slashes (C:/Users/...). Windows and PowerShell support forward slashes perfectly, and it completely avoids JSON escaping issues!

Example of a clean Windows configuration in settings.json:

{
  "statusLine": {
    "command": "powershell.exe -ExecutionPolicy Bypass -File C:/Users/YourUsername/.gemini/antigravity-cli/statusline.ps1",
    "enabled": true
  }
}

3. Terminal Width Auto-Collapse

The CLI interface is built using ink (React for terminal), which has a built-in safety layout guard.

• The Problem: If your terminal window is too narrow, the CLI dynamically hides the footer/statusline to prevent layout wrapping bugs.
• The Fix: Try maximizing or resizing your terminal window to a width of at least 120 columns, then restart agy.

4. Step-by-Step Diagnostic Test

To verify if everything is wired correctly, run this test in your PowerShell window:

1. First, check if the JSON is valid and the script parses it correctly by running:

   '{"agent_state": "thinking", "workspace": {"current_dir": "C:\\Project"}}' | powershell.exe -ExecutionPolicy Bypass -File C:/Users/YourUsername/.gemini/antigravity-cli/statusline.ps1

2. Check the CLI logs for any launch errors. Go to your local logs folder:
   %APPDATA%\antigravity-cli\log\
   Open the latest log file and search for statusLine or execution errors.

---

⚡ Pro-Tip: Switch to Node.js for zero lag!

PowerShell (powershell.exe or pwsh.exe) has a relatively heavy startup overhead (500ms to 1s). Since the status line runs frequently in the TUI, executing PowerShell on every tick can cause minor interface lags on Windows.

We highly recommend using the native Node.js implementation (statusline.js), which starts up instantly (~50ms) and has zero external dependencies (no jq required).

Simply configure it in settings.json:

{
  "statusLine": {
    "command": "node C:/Users/YourUsername/.gemini/antigravity-cli/statusline.js",
    "enabled": true
  }
}

Let us know if this brings the status line to life for you! 🚀

[weby-homelab]

The provided script for PowerShell Core is perfect. ❤️

However, it still unable to display as expected at the bottom of Antigravity CLI. Should I place the script to somewhere else? Is `~/.gemini/antigravity-cli/` itself a "protected zone" so Antigravity CLI cannot load executable scripts in it?

PixPin_2026-05-29_11-38-08_1.mp4

It looks like you're encountering two separate issues here:

1. Manual Testing Issue (The 0.0% Context)
   In your screenshot, you are piping a JSON block into statusline.ps1, but you've included the comment line at the very top:
   // This section was copied from https://antigravity.google/...

Standard JSON does not support comments. Because of this line, ConvertFrom-Json inside the script fails to parse the payload and returns $null. As a result, the script falls back to its default values, which is why it displays 0.0% and sandbox off.

Fix: Remove the // comment line and pipe only the clean JSON object starting directly with {. For example:

PowerShell:

@"
{
  "cwd": "/home/user/my-project",
  "context_window": {
    "used_percentage": 8.415603637695312
  }
  ...
}
"@ | pwsh.exe -ExecutionPolicy Bypass -File .\bin\statusline.ps1

2. CLI Behavior (/statusline toggle)
   In your video, you toggled /statusline on and then immediately off inside the interactive TUI because no immediate visual changes appeared.

Please note that the /statusline command doesn't change the internal UI of agy.exe. Instead, it enables the CLI to output state data so it can be integrated into your external shell prompt (your main PowerShell prompt).

Fix: > 1. Run agy.exe and turn it back on using /statusline (so that enabled becomes True in your settings.json).
2. Exit the CLI and integrate the script into your PowerShell $PROFILE as described in the documentation to see the dynamic status line in your actual terminal.

[Dragon1573]

• bug: /statusline slash command does not open the status line configuration interface #74 (comment)

Backslashes have already escaped.

However, data extracted from JSON seems still incorrect.

---

Please note that the /statusline command doesn't change the internal UI of agy.exe. Instead, it enables the CLI to output state data so it can be integrated into your external shell prompt (your main PowerShell prompt).

😕 I can't get it.

Where is the referenced status line? Why it's used as "external shell prompt"? I just want it shown as the status line "footer" of Antigravity CLI - like Gemini CLI do.

[Dragon1573]

Nodejs version also failed to parse piped JSON.

18:24:35 ~\...\bin 0ms pwsh
$ Write-Output @"
> {
>   "cwd": "/home/user/my-project",
>   "conversation_id": "12345678-abcd-ef01-2345-6789abcdef01",
>   "model": {
>     "id": "Gemini",
>     "display_name": "Gemini"
>   },
>   "workspace": {
>     "current_dir": "/home/user/my-project",
>     "project_dir": "file:///home/user/my-project"
>   },
>   "version": "2026.04.15",
>   "context_window": {
>     "total_input_tokens": 88244,
>     "total_output_tokens": 61074,
>     "context_window_size": 1048576,
>     "used_percentage": 8.415603637695312,
>     "remaining_percentage": 91.58439636230469,
>     "current_usage": {
>       "input_tokens": 63382,
>       "output_tokens": 346,
>       "cache_creation_input_tokens": 0,
>       "cache_read_input_tokens": 20857
>     }
>   },
>   "product": "antigravity-cli",
>   "agent_state": "idle",
>   "vcs": {
>     "type": "git",
>     "client": "my-project",
>     "branch": "dev",
>     "dirty": false
>   },
>   "sandbox": {
>     "enabled": false
>   },
>   "plan_tier": "Pro",
>   "email": "developer@email.com",
>   "terminal_width": 111
> }
> "@ | node statusline.js
╭─ ● READY
╰─ ctx ··············· 0.0% · 📦 0 · 🤖 0 · ⏳ 0 · 🛡️ sandbox off

[Dragon1573]

It seems you're reading stdin with a wrong implementation.

According to GitHub Copilot, it's suggested as follows:

# ─── Read JSON from stdin ────────────────────────────────────────────────────
# Read all piped input
[cmdletBinding()]
param(
    [Parameter(ValueFromPipeline)]
    [string]$inputJson
)

if ([string]::IsNullOrWhiteSpace($inputJson)) {
    $inputJson = '{}'
}

try {
    $data = ConvertFrom-Json $inputJson -ErrorAction SilentlyContinue
} catch {
    $data = $null
}

if ($null -eq $data) {
    $data = [PSCustomObject]@{}
}

19:12:01 D:\...\winget-pkgs  [master +2 ~0 -0 !] 0ms pwsh
$ echo @"                                                            
> {
>   "cwd": "/home/user/my-project",
>   "conversation_id": "12345678-abcd-ef01-2345-6789abcdef01",
>   "model": {
>     "id": "Gemini",
>     "display_name": "Gemini"
>   },
>   "workspace": {
>     "current_dir": "/home/user/my-project",
>     "project_dir": "file:///home/user/my-project"
>   },
>   "version": "2026.04.15",
>   "context_window": {
>     "total_input_tokens": 88244,
>     "total_output_tokens": 61074,
>     "context_window_size": 1048576,
>     "used_percentage": 8.415603637695312,
>     "remaining_percentage": 91.58439636230469,
>     "current_usage": {
>       "input_tokens": 63382,
>       "output_tokens": 346,
>       "cache_creation_input_tokens": 0,
>       "cache_read_input_tokens": 20857
>     }
>   },
>   "product": "antigravity-cli",
>   "agent_state": "idle",
>   "vcs": {
>     "type": "git",
>     "client": "my-project",
>     "branch": "dev",
>     "dirty": false
>   },
>   "sandbox": {
>     "enabled": false
>   },
>   "plan_tier": "Pro",
>   "email": "developer@email.com",
>   "terminal_width": 111
> }
> "@ | C:\Users\Dragon1573\.gemini\antigravity-cli\bin\statusline.ps1
╭─ ● READY ╱ Gemini ╱ git:dev ╱ 📂 /home/user/my-project
╰─ ctx █·············· 8.4% (149.3K/1.0M) · 📦 0 · 🤖 0 · ⏳ 0 · 🛡️ sandbox off

[weby-homelab]

Hi @Dragon1573,

It looks like there was some confusion about how the custom status line is rendered, as well as a couple of Windows/PowerShell pathing and pipeline issues. We have resolved these and updated the pull request!

1. Clarification: Status Line in the Interactive CLI TUI

First, to clarify: the /statusline setting in settings.json does indeed customize the status line footer directly inside the interactive TUI of agy.exe (just like it did in the old Gemini CLI). The previous comment was incorrect in stating that it only outputs state data for an external shell prompt.
If agy.exe falls back to the default minimal status bar (? for shortcuts | Gemini), it means the custom status line command failed to execute or returned an error.

2. Windows Pathing & Executable Shorthands

On Windows, several platform-specific friction points prevent the script from running directly from settings.json:

• Tilde (~) shorthand: The Go-compiled binary (agy.exe) spawns the subprocess directly and does not expand the ~ shorthand. You must specify the full absolute path (e.g., C:/Users/YourUsername/.gemini/...).
• Path Escaping: Standard backslashes in paths (C:\Users) act as escape sequences in JSON. It is highly recommended to use forward slashes (C:/Users/YourUsername/...) in settings.json, which avoids escaping errors and works perfectly on Windows.
• Direct Execution: Windows does not execute .ps1 or .js files directly. You must specify the interpreter:
  • For Node.js: "command": "node C:/Users/YourUsername/.gemini/antigravity-cli/bin/statusline.js"
  • For PowerShell: "command": "powershell.exe -ExecutionPolicy Bypass -File C:/Users/YourUsername/.gemini/antigravity-cli/bin/statusline.ps1"

3. Pipeline / Stdin Input Parsing Fixes

The original PowerShell implementation was reading input using [Console]::In.ReadToEnd(). While this works when run by agy (which redirects standard input), it fails when testing the script manually via a PowerShell pipeline (e.g. $json | .\statusline.ps1), because PowerShell pipelines pass objects/strings internally and do not redirect console stdin.
We have updated both statusline.ps1 and title.ps1 to support both execution methods seamlessly by accepting pipeline parameters with a fallback to stdin reading:

param(
    [Parameter(ValueFromPipeline)]
    [string]$inputJson
)
if ([string]::IsNullOrWhiteSpace($inputJson)) {
    $inputJson = [Console]::In.ReadToEnd()
}
# ...

This enables seamless pipeline testing like:

$json | .\statusline.ps1

while maintaining compatibility with agy's direct stdin redirection.

4. Better JSON Error Formatting

We also added try-catch blocks to Node.js and PowerShell scripts. If invalid JSON is passed (e.g. from copy-pasting syntax errors, like the "produ typo), the scripts will print the parsing error directly in red text on the status line, making it much easier to diagnose configuration issues.

We have pushed these updates to the active PR #206. Feel free to grab the updated files from there and verify them! 🚀

[Dragon1573]

21:11:24 D:\...\winget-pkgs  [master ≡] 0ms pwsh
$ Get-Content C:\Users\Dragon1573\.gemini\antigravity-cli\settings.json |
> ConvertFrom-Json | Select-Object -ExpandProperty statusline |
> Format-List

type    : command
command : pwsh.exe C:\Users\Dragon1573\.gemini\antigravity-cli\bin\statusline.ps1
enabled : True

.ps1 contents

# ─── Read JSON from stdin ────────────────────────────────────────────────────
# Read all piped input
[cmdletBinding()]
param(
    [Parameter(ValueFromPipeline)]
    [string]$inputJson
)

if ([string]::IsNullOrWhiteSpace($inputJson)) {
    $inputJson = '{}'
}

try {
    $data = ConvertFrom-Json $inputJson -ErrorAction SilentlyContinue
} catch {
    $data = $null
}

if ($null -eq $data) {
    $data = [PSCustomObject]@{}
}

# ─── ANSI Helpers (Standard 16-color palette only) ───────────────────────────
$R = "$([char]0x1b)[0m"         # Reset
$B = "$([char]0x1b)[1m"         # Bold
$D = "$([char]0x1b)[2m"         # Dim
$I = "$([char]0x1b)[3m"         # Italic

# Foreground accents (Standard 16 colors)
$FG_BLACK = "$([char]0x1b)[30m"
$FG_RED = "$([char]0x1b)[31m"
$FG_GREEN = "$([char]0x1b)[32m"
$FG_YELLOW = "$([char]0x1b)[33m"
$FG_BLUE = "$([char]0x1b)[34m"
$FG_MAGENTA = "$([char]0x1b)[35m"
$FG_CYAN = "$([char]0x1b)[36m"
$FG_WHITE = "$([char]0x1b)[37m"

$FG_GRAY = "$([char]0x1b)[90m"
$FG_BRIGHT_RED = "$([char]0x1b)[91m"
$FG_BRIGHT_GREEN = "$([char]0x1b)[92m"
$FG_BRIGHT_YELLOW = "$([char]0x1b)[93m"
$FG_BRIGHT_BLUE = "$([char]0x1b)[94m"
$FG_BRIGHT_MAGENTA = "$([char]0x1b)[95m"
$FG_BRIGHT_CYAN = "$([char]0x1b)[96m"
$FG_BRIGHT_WHITE = "$([char]0x1b)[97m"

$NUM_COLOR = "${FG_BRIGHT_WHITE}${B}"

# ─── Extract fields with fallback ────────────────────────────────────────────
$state = if ($data.agent_state) { $data.agent_state } else { "idle" }
$usedPct = if ($data.context_window -and $null -ne $data.context_window.used_percentage) { [double]$data.context_window.used_percentage } else { 0.0 }
$vcsBranch = if ($data.vcs -and $data.vcs.branch) { $data.vcs.branch } else { "" }
$vcsDirty = if ($data.vcs -and $null -ne $data.vcs.dirty) { $data.vcs.dirty } else { $false }
$vcsType = if ($data.vcs -and $data.vcs.type) { $data.vcs.type } else { "" }
$sandboxEnabled = if ($data.sandbox -and $null -ne $data.sandbox.enabled) { $data.sandbox.enabled } else { $false }
$sandboxNet = if ($data.sandbox -and $null -ne $data.sandbox.allow_network) { $data.sandbox.allow_network } else { $false }
$artifactCount = if ($data.artifact_count) { $data.artifact_count } else { 0 }
$subagentsCount = if ($data.subagents) { @($data.subagents).Count } else { 0 }
$taskCount = if ($data.task_count) { $data.task_count } else { 0 }
$modelId = if ($data.model -and $data.model.id) { $data.model.id } else { "" }
$modelName = if ($data.model -and $data.model.display_name) { $data.model.display_name } else { "" }
$cols = if ($data.terminal_width) { [int]$data.terminal_width } else { 80 }
$cwd = if ($data.cwd) { $data.cwd } else { "" }
$convId = if ($data.conversation_id) { $data.conversation_id } else { "" }
$inputTokens = if ($data.context_window -and $null -ne $data.context_window.total_input_tokens) { $data.context_window.total_input_tokens } else { 0 }
$outputTokens = if ($data.context_window -and $null -ne $data.context_window.total_output_tokens) { $data.context_window.total_output_tokens } else { 0 }
$ctxLimit = if ($data.context_window -and $null -ne $data.context_window.context_window_size) { $data.context_window.context_window_size } else { 0 }
$ctxUsed = $inputTokens + $outputTokens

# ─── Helper Functions ────────────────────────────────────────────────────────
function Get-HumanFormat {
    param ($num)
    if ($null -eq $num -or $num -eq 0) { return "0" }
    if ($num -ge 1000000) {
        $main = [Math]::Floor($num / 1000000)
        $dec = [Math]::Floor(($num % 1000000) / 100000)
        return "${main}.${dec}M"
    }
    if ($num -ge 1000) {
        $main = [Math]::Floor($num / 1000)
        $dec = [Math]::Floor(($num % 1000) / 100)
        return "${main}.${dec}K"
    }
    return "$num"
}

function Get-ShortenPath {
    param ($path)
    if ([string]::IsNullOrEmpty($path)) { return "" }
    $homePath = $env:USERPROFILE
    if (-not $homePath) {
        $homePath = $env:HOME
    }
    if ($homePath -and $path.StartsWith($homePath)) {
        $path = "~" + $path.Substring($homePath.Length)
    }
    if ($path.Length -gt 25) {
        $leaf = Split-Path $path -Leaf
        return "...$leaf"
    }
    return $path
}

$cwdShort = Get-ShortenPath $cwd

# ─── State Indicator ──────────────────────────────────────────────────────────
switch ($state) {
    "idle"     { $S = "${FG_BRIGHT_GREEN}${B}● READY${R}" }
    "thinking" { $S = "${FG_BRIGHT_YELLOW}${B}◆ THINKING${R}" }
    "working"  { $S = "${FG_BRIGHT_CYAN}${B}⚙ WORKING${R}" }
    "tool_use" { $S = "${FG_BRIGHT_MAGENTA}${B}🔧 TOOL${R}" }
    Default    { $S = "${FG_WHITE}${B}⏳ $($state.ToUpper())${R}" }
}

# ─── VCS Branch & Type ───────────────────────────────────────────────────────
$V = ""
if (-not [string]::IsNullOrEmpty($vcsBranch)) {
    $vcsLabel = if (-not [string]::IsNullOrEmpty($vcsType)) { $vcsType } else { "git" }
    if ($vcsDirty -eq $true -or $vcsDirty -eq "true") {
        $V = "${FG_GRAY} ╱ ${FG_GRAY}${vcsLabel}:${FG_BRIGHT_RED}${vcsBranch}${FG_BRIGHT_YELLOW}*${R}"
    } else {
        $V = "${FG_GRAY} ╱ ${FG_GRAY}${vcsLabel}:${FG_BRIGHT_BLUE}${vcsBranch}${R}"
    }
}

# ─── Model ───────────────────────────────────────────────────────────────────
$modelDisp = if (-not [string]::IsNullOrEmpty($modelName)) { $modelName } else { $modelId }
$M = ""
if (-not [string]::IsNullOrEmpty($modelDisp)) {
    $M = "${FG_GRAY} ╱ ${FG_BRIGHT_MAGENTA}${I}${modelDisp}${R}"
}

# ─── Sandbox Badge ───────────────────────────────────────────────────────────
if ($sandboxEnabled -eq $true -or $sandboxEnabled -eq "true") {
    if ($sandboxNet -eq $true -or $sandboxNet -eq "true") {
        $SB = "${FG_GRAY}🛡️ sandbox ${FG_BRIGHT_GREEN}${B}ON (net)${R}"
    } else {
        $SB = "${FG_GRAY}🛡️ sandbox ${FG_BRIGHT_GREEN}${B}ON (no-net)${R}"
    }
} else {
    $SB = "${FG_GRAY}🛡️ sandbox off${R}"
}

# ─── Context Bar ─────────────────────────────────────────────────────────────
$BAR_LEN = 15
$pctInt = [int][Math]::Floor($usedPct)
$filled = [int][Math]::Floor($pctInt * $BAR_LEN / 100)
$remainder = ($pctInt * $BAR_LEN) % 100

$barColor = $FG_BRIGHT_WHITE
if ($pctInt -ge 90) {
    $barColor = $FG_BRIGHT_RED
} elseif ($pctInt -ge 60) {
    $barColor = $FG_BRIGHT_YELLOW
}

$BAR = ""
for ($i = 0; $i -lt $BAR_LEN; $i++) {
    if ($i -lt $filled) {
        $BAR += "█"
    } elseif ($i -eq $filled) {
        if ($remainder -ge 75) {
            $BAR += "▓"
        } elseif ($remainder -ge 50) {
            $BAR += "▒"
        } elseif ($remainder -ge 25) {
            $BAR += "░"
        } else {
            $BAR += "·"
        }
    } else {
        $BAR += "·"
    }
}

# ─── Stats Formatting ────────────────────────────────────────────────────────
$pctFmt = $usedPct.ToString("0.0", [System.Globalization.CultureInfo]::InvariantCulture)
$CTX_BAR = "${FG_GRAY}ctx ${barColor}${BAR} ${NUM_COLOR}${pctFmt}%${R}"
$ART_FMT = "${FG_GRAY}📦 ${NUM_COLOR}${artifactCount}${R}"
$SUB_FMT = "${FG_GRAY}🤖 ${NUM_COLOR}${subagentsCount}${R}"
$BG_FMT = "${FG_GRAY}⏳ ${NUM_COLOR}${taskCount}${R}"

$DIR_FMT = ""
if (-not [string]::IsNullOrEmpty($cwdShort)) {
    $DIR_FMT = "${FG_GRAY} ╱ 📂 ${cwdShort}${R}"
}

$CONV_FMT = ""
if (-not [string]::IsNullOrEmpty($convId)) {
    $subConvId = if ($convId.Length -gt 8) { $convId.Substring(0, 8) } else { $convId }
    $CONV_FMT = "${FG_GRAY} ╱ id:${subConvId}${R}"
}

$tokDetails = ""
if ($ctxUsed -gt 0) {
    $ctxUsedFmt = Get-HumanFormat $ctxUsed
    $ctxLimitFmt = Get-HumanFormat $ctxLimit
    $tokDetails = " (${ctxUsedFmt}/${ctxLimitFmt})"
}

$DOT = "${FG_GRAY} · ${R}"

# ─── Output Assembly ──────────────────────────────────────────────────────────
if ($cols -ge 120) {
    $line1 = "${S}${M}${V}${DIR_FMT}${CONV_FMT}"
    if ($ctxUsed -gt 0) {
        $ctxUsedFmt = Get-HumanFormat $ctxUsed
        $ctxLimitFmt = Get-HumanFormat $ctxLimit
        $inputTokFmt = Get-HumanFormat $inputTokens
        $outputTokFmt = Get-HumanFormat $outputTokens
        $tokDetails = " (${ctxUsedFmt}/${ctxLimitFmt} · ${inputTokFmt} in/${outputTokFmt} out)"
    }
    $line2 = " ${CTX_BAR}${tokDetails}${DOT}${ART_FMT}${DOT}${SUB_FMT}${DOT}${BG_FMT}${DOT}${SB}"
    Write-Output "${line1}${FG_GRAY}  │  ${R}${line2}"
} elseif ($cols -ge 80) {
    $line1 = "${S}${M}${V}${DIR_FMT}"
    $line2 = " ${CTX_BAR}${tokDetails}${DOT}${ART_FMT}${DOT}${SUB_FMT}${DOT}${BG_FMT}${DOT}${SB}"
    Write-Output "${FG_GRAY}╭─${R} ${line1}"
    Write-Output "${FG_GRAY}╰─${R}${line2}"
} else {
    $mShort = ""
    if (-not [string]::IsNullOrEmpty($modelDisp)) {
        $subModelDisp = if ($modelDisp.Length -gt 12) { $modelDisp.Substring(0, 12) } else { $modelDisp }
        $mShort = "${FG_GRAY} ╱ ${FG_BRIGHT_MAGENTA}${subModelDisp}${R}"
    }
    Write-Output "${S}${mShort}"
    Write-Output "${CTX_BAR}${DOT}${BG_FMT}"
}

[Dragon1573]

if ([string]::IsNullOrWhiteSpace($inputJson)) {
    $inputJson = [Console]::In.ReadToEnd()
}

😕 Even though this modification, footer zone of agy.exe is still blank.

[weby-homelab]

my Friend, if you already have ANTIGRAVITY-CLI installed and working, then ask it to set up the /statusline for you,
as I did and everything worked out well))