Do I need a terminal to use standards?
Short answer
Not to read them: GilbApp shows them; GilbPlatform's rule says no standard or tool needs a terminal, yet setting up Claude Code uses one today.
Before you start
Words used here (2)
- GilbApp
- GilbApp is the app, opened in a web browser at https://gilb.com/app, where you open, fill and share your vaults.
- GilbPlatform
- GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
Deeper
A terminal is a window for typing commands, such as Terminal on a Mac. Standards are kept on GilbPlatform; a standard is a written procedure, rule set, form or other guide that people and agents follow as they work. To read one you need no terminal: in GilbApp, Standards in the GO TO panel shows them by kind, under the tabs Policies, Processes, Procedures, Rules, Templates & Forms, Checklists, References and Lookups. The answer on reading a standard shows how.
The rule is the standard GilbPlatform.NoHumanTerminal (© 2026 Kai Gilb). It says that no GilbPlatform standard or tool requires the user to use a terminal. Where a terminal is technically unavoidable, the standard names that step, says why no other way works, and names who reviews it. An agent, your AI following one written procedure, runs every other step; you do not type it.
The command your AI uses to read a standard from your computer, kz-std, runs in a terminal, but your AI runs it there itself; you do not type it. The answer on what a standard reader's exit codes mean is for people who look at that command.
Setting up your own AI is another matter today. GilbApp has no steps for using Grok in Terminal: GilbApp's chat connects Grok through xAI's site, and you install nothing. Claude Code is installed by pasting lines in Terminal, as the answer on installing Claude Code shows. It is connected to GilbApp's chat or to your vault the same way, as the answer on connecting your AI to GilbApp chat and the one on connecting your computer to your vault show. None of the standards read for this answer names those as the unavoidable terminal steps the rule asks for.
Source: Standards read 10 November 2026: GilbPlatform.NoHumanTerminal (J 06gjntjve1rr5256jh9px6gwn4, RuleSet, 3 rules): NoStep (No GilbPlatform standard or tool requires the user to use a terminal.), Exception ("Where a terminal is technically unavoidable, the standard names that step, says why no other way works, and names who reviews it."), Agent (An agent runs every other step. The user does not type it.). The standard reader kz-std (commit dc8d1ca8, 13 October 2026): kz-std.mjs lines 2-5 ("read a Kai-Zen standard from the platform, in a terminal. An AI agent runs this through its own shell"); SETUP.md:3-5 (Replaced 2026-09-25. Your AI now does this setup for you); GilbPlatform 4d008a55 scripts/devkit/README.md:18-19 (the setup link installs kz-std; unchanged at the live 498d29a0). GilbApp af0f04ee (cited files unchanged at the live ebd9415e, compared 11 November 2026): shell/gilbAppMenuRows.ts:220-230 (Standards), components/process/standardsTabs.ts:9-25 (the eight tabs). Published answers (agreement): How do I install Claude Code? (Terminal), How do I connect my AI to GilbApp chat? (paste a line in Terminal for Claude Code), How do I connect my computer to my vault? (paste its first five lines in Terminal), Can I use any AI, not only Claude Code or Grok? (GilbApp has no steps for Grok in Terminal.; Terminal gloss), What do I need to get started? (Grok: GilbApp's chat connects it through xAI's site, you install nothing), How do I see which standing instructions an agent loaded? and How do I make my own agent? (standards and agent glosses). xAI's own terminal coding tool Grok Build: https://docs.x.ai/build/overview (read 13 November 2026). The three standards read for this group (Licence, StandardRules, NoHumanTerminal) name no unavoidable terminal step.
Checked against GilbApp d529620.