Gajae Code

Tool guide

computer desktop-control tool

Tell your GJC session to use the computer tool when it needs to see the local screen, click, type, scroll, or drive a desktop app.

How to use it

There is no separate gjc computer subcommand. The tool is available only on macOS and is disabled unless computer.enabled=true (for the current session) or computer.alwaysOn=true (persistent) is set. Start a normal GJC session after enabling one of those settings, then ask the agent to use the computer tool.

# 1. Enable the tool in the session or persistent settings
# computer.enabled=true  (current session)
# computer.alwaysOn=true (persistent)

# 2. Launch GJC from the repo/workspace where you want the agent to work
gjc

# 3. In your prompt, be explicit
"Use the computer tool to inspect the app window, click the login button, and type the test account."

# 4. Keep the kill-switch available
# Default: Control+Option+Command+Escape

What it can do

The tool uses this exact nine-action set:

  • screenshot — capture the current primary display.
  • click, double_click, move, drag, scroll — pointer control.
  • type, keypress — keyboard input.
  • wait — bounded timing.

The screenshot's pixel dimensions are the coordinate space. Use coordinates from the latest screenshot; native code maps them to macOS logical points and rejects stale or invalid coordinates before input.

Platform and permissions

  • Platform: macOS. Linux and Windows are not callable computer-tool platforms.
  • Enablement: set computer.enabled=true for a session or computer.alwaysOn=true to keep it enabled. Without either flag, every action returns COMPUTER_DISABLED.
  • Permissions: Screen Recording and Accessibility are required. Missing permissions are surfaced as explicit errors rather than silent black screenshots.
  • Safety: the global kill-switch is outside model control and can stop queued input, release held buttons/keys, and suspend further computer actions.

This is an experimental, opt-in surface. Use it for local desktop coordination where visual feedback matters, and verify important actions before relying on them.

Prompt examples

Use the computer tool to take a screenshot and tell me what app is frontmost.

Use the computer tool to click the first empty row in the spreadsheet and type this CSV row.

Use the computer tool to open the browser window, inspect the error banner, and stop after the screenshot.

Keep prompts concrete: name the visible app, the action to perform, and the stop condition.