Gaia Tui Manual logo

Gaia Tui Manual

OrganizationPopular
amd
gaia-tui-manual

The GAIA terminal UI (gaia-tui) — how to build it, launch it with a real pty, drive it through the loopback control API, choose a local or cloud model provider, and read its logs. Use when running, testing, debugging, or documenting the TUI, when a preflight row blocks a launch, when driving the TUI from a script or assistant, or when a TUI question would otherwise be answered by guessing at the Go source.

Overview

Publisheramd
Repositorygaia
Skill namegaia-tui-manual
Stars
1.6K
Forks
176
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by amd on GitHub. Read the source before you install it.

Installation

Install the Gaia Tui Manual AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/amd/gaia/tree/main/.claude/skills/gaia-tui-manual
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/amd/gaia.git /tmp/gaia
mkdir -p .claude/skills
cp -r /tmp/gaia/.claude/skills/gaia-tui-manual .claude/skills/gaia-tui-manual
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gaia Tui Manual in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gaia Tui Manual on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gaia Tui Manual is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

GAIA Terminal UI

Two manuals carry the detail. Read the matching one before touching the TUI — both are written from verified runs, not from reading the source.

  • User manual (docs/guides/terminal-hub.mdx) — install, the setup gate and what each row means, choosing where inference runs, day-to-day use, the permission prompt, troubleshooting.
  • Developer manual (docs/reference/tui-dev.mdx) — the three-process architecture, building, the full control-API reference, pty allocation, logs and traces, and running a local model on a dev box.

.claude/skills/driving-the-tui/ covers the same control API from the assistant's side; the developer manual is the reference it defers to for endpoint shapes.

The five things that waste the most time

Each of these cost a real debugging session. They are in the manuals too — this is the short list worth carrying in your head.

  1. The agent subprocess outlives your edits. gaia-tui spawns gaia-agent once. Change Python under src/gaia/ or hub/agents/ and the running session keeps executing the old code — a before/after measurement taken without a restart is two measurements of the same build. Restart the TUI.

  2. keys takes an array. {"keys": ["p"]}. A bare string is rejected with cannot unmarshal string into Go struct field keysRequest.keys of type []string. text types but does not submit — follow with ["enter"].

  3. It needs a real pty. script fails on a socket (tcgetattr/ioctl: Operation not supported), and driving Terminal.app via osascript can time out with -1712 and leave nothing running. Allocate the pty yourself with pty.fork(), size it with TIOCSWINSZ, and drain the fd or the child blocks. Call resize first in any drive script.

  4. Wait, never sleep — POST /control/v1/wait blocks server-side on contains / absent / state. But {"state":{"streaming":false}} can match the instant before a turn starts; confirm streaming went true first, or poll status.

  5. The "Language model" preflight row includes the embedder. A machine with a working chat model still blocks on the ~300 MB user.embeddinggemma-300m-GGUF, while the row says "Several GB". gaia init --check names the exact missing id.

Before reporting a TUI bug

  • Capture the whole screen. A cropped capture once produced a fabricated "uninstall silently does nothing" — the status line is the second-to-last row.
  • Check view in status before sending keys; keys sent to the wrong screen do nothing and read as a broken binding.
  • Check the TOOL_LOADER lines in ~/.gaia/logs/gaia-agent.log before believing the agent when it says a capability "isn't available" — it may simply not have been selected for that turn.
  • Say which branch you built. Stacked branches are siblings; a leaf build shows behaviour already fixed elsewhere.

Frequently asked questions

What does the Gaia Tui Manual AI skill do?

The GAIA terminal UI (gaia-tui) — how to build it, launch it with a real pty, drive it through the loopback control API, choose a local or cloud model provider, and read its logs. Use when running, testing, debugging, or documenting the TUI, when a preflight row blocks a launch, when driving the TUI from a script or assistant, or when a TUI question would otherwise be answered by guessing at the Go source.

Why use Gaia Tui Manual on TypingMind?

Because you install it once and use it with any model. Gaia Tui Manual is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gaia Tui Manual in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/amd/gaia/tree/main/.claude/skills/gaia-tui-manual. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Gaia Tui Manual?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gaia Tui Manual?

As many as you like. As long as a model supports skills, you can use Gaia Tui Manual with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gaia Tui Manual AI skill free?

Yes. It is published on GitHub by amd under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇