Skip to content
The Terminal

Gee-Code + The Terminal

import { Steps, Aside } from ‘@astrojs/starlight/components’;

The Terminal was built for Gee-Code — an AI coding assistant that runs in your terminal. When Gee-Code runs inside The Terminal, it gains a capability no other AI tool has: it can see your running application.

How It Works

Section titled “How It Works”

  1. You run Gee-Code in a terminal panel

    Just type gee-code in any Terminal panel. It detects The Terminal automatically.

  2. Gee-Code reads the DevTools config

    On startup, Gee-Code checks ~/.the-terminal/devtools.json for the browser panel’s DevTools API endpoint.

  3. Connection established

    Gee-Code connects to the browser panel’s DevTools protocol. It can now read console output, inspect the DOM, execute JavaScript, take screenshots, and interact with the page.

  4. You work normally

    Run your dev server in one terminal panel, point the browser at it, and talk to Gee-Code in another panel. It sees everything.

What Changes

Section titled “What Changes”

Without The Terminal, Gee-Code is an excellent CLI coding assistant — it can read files, write code, run commands, and search the web. But when it comes to your running application, it’s blind. You have to describe what you see.

With The Terminal:

WithoutWith The Terminal
”There’s an error in the console”Gee-Code reads the error directly
”The page is blank”Gee-Code takes a screenshot and sees it
”The button doesn’t work”Gee-Code clicks the button and observes what happens
”The API returns the wrong data”Gee-Code reads the network response

Setup

Section titled “Setup”

No configuration needed. If Gee-Code is installed and you run it inside The Terminal, the connection is automatic.

Prerequisites:

  • The Terminal installed and running
  • Gee-Code installed (pip install gee-code)
  • At least one browser panel open

Example Session

Section titled “Example Session”
You: My React dashboard is showing "loading..." forever


Gee-Code:
  ✓ Connected to browser panel (localhost:3000)
  ✓ Console shows: "Failed to fetch: 401 Unauthorized"
  ✓ Network tab: GET /api/dashboard → 401
  ✓ Reading src/api/client.js...
  ✓ Issue: Auth token not being sent in request headers
  ✓ Fixed: Added Authorization header to API client
  ✓ Browser refreshed — dashboard loads correctly

The entire debugging cycle — observe, diagnose, fix, verify — happened without you copying a single error message.

Gee-Code Features in The Terminal

Section titled “Gee-Code Features in The Terminal”

When running inside The Terminal, Gee-Code gains these additional tools:

  • DevBrowserConnect — connect to the browser panel
  • DevBrowserConsole — read console logs, warnings, and errors
  • DevBrowserDom — inspect DOM structure
  • DevBrowserEval — execute JavaScript in the page
  • DevBrowserScreenshot — capture the current page
  • DevBrowserClick — click elements
  • DevBrowserFill — fill form inputs
  • DevBrowserNetwork — read network requests

These tools are only available when Gee-Code detects The Terminal’s DevTools API.

Next Steps

Section titled “Next Steps”