@humain/terminal 0.0.2 → 0.0.3-beta.0

package/README.md

@@ -1,28 +1,38 @@
-<h1 align="center">HUMAIN Terminal</h1>
-<p align="center">The terminal companion for HUMAIN Code.</p>
+<p align="center">
+  <a href="https://pi.dev">
+    <img alt="pi logo" src="https://pi.dev/logo-auto.svg" width="128">
+  </a>
+</p>
 <p align="center">
   <a href="https://discord.com/invite/3cU7Bz4UPx"><img alt="Discord" src="https://img.shields.io/badge/discord-community-5865F2?style=flat-square&logo=discord&logoColor=white" /></a>
+  <a href="https://www.npmjs.com/package/@earendil-works/pi-coding-agent"><img alt="npm" src="https://img.shields.io/npm/v/@earendil-works/pi-coding-agent?style=flat-square" /></a>
 </p>
 
 > New issues and PRs from new contributors are auto-closed by default. Maintainers review auto-closed issues daily. See [CONTRIBUTING.md](../../CONTRIBUTING.md).
 
 ---
 
-HUMAIN Terminal is a model-flexible terminal coding harness for internal HUMAIN engineering and client-facing workflows. It uses an upstream-compatible extension/runtime model under the hood, but presents HUMAIN branding, HUMAIN defaults, SSO-ready login, Forge-aware routing, local model support, and bundled productivity extensions.
+Pi is a minimal terminal coding harness. Adapt pi to your workflows, not the other way around, without having to fork and modify pi internals. Extend it with TypeScript [Extensions](#extensions), [Skills](#skills), [Prompt Templates](#prompt-templates), and [Themes](#themes). Put your extensions, skills, prompt templates, and themes in [Pi Packages](#pi-packages) and share them with others via npm or git.
 
-Adapt HUMAIN Terminal to your workflows without forking internals. Extend it with TypeScript [Extensions](#extensions), [Skills](#skills), [Prompt Templates](#prompt-templates), [Themes](#themes), and [Packages](#packages).
+Pi ships with powerful defaults but skips features like sub agents and plan mode. Instead, you can ask pi to build what you want or install a third party pi package that matches your workflow.
 
-HUMAIN Terminal runs in four modes: interactive, print or JSON, RPC for process integration, and an SDK for embedding in your own apps.
+Pi runs in four modes: interactive, print or JSON, RPC for process integration, and an SDK for embedding in your own apps.
 
 ## Share your OSS coding agent sessions
 
-If you use HUMAIN Terminal for open source work, you can publish coding agent sessions.
+If you use pi for open source work, please share your coding agent sessions.
 
 Public OSS session data helps improve models, prompts, tools, and evaluations using real development workflows.
 
 For the full explanation, see [this post on X](https://x.com/badlogicgames/status/2037811643774652911).
 
-To publish sessions, use a HUMAIN-approved session exporter. All you need is a Hugging Face account, the Hugging Face CLI, and an exporter configured for the HUMAIN Terminal session format.
+To publish sessions, use [`badlogic/pi-share-hf`](https://github.com/badlogic/pi-share-hf). Read its README.md for setup instructions. All you need is a Hugging Face account, the Hugging Face CLI, and `pi-share-hf`.
+
+You can also watch [this video](https://x.com/badlogicgames/status/2041151967695634619), where I show how I publish my `pi-mono` sessions.
+
+I regularly publish my own `pi-mono` work sessions here:
+
+- [badlogicgames/pi-mono on Hugging Face](https://huggingface.co/datasets/badlogicgames/pi-mono)
 
 ## Table of Contents
 
@@ -43,7 +53,7 @@ To publish sessions, use a HUMAIN-approved session exporter. All you need is a H
   - [Skills](#skills)
   - [Extensions](#extensions)
   - [Themes](#themes)
-  - [Packages](#packages)
+  - [Pi Packages](#pi-packages)
 - [Programmatic Usage](#programmatic-usage)
 - [Philosophy](#philosophy)
 - [CLI Reference](#cli-reference)
@@ -53,26 +63,32 @@ To publish sessions, use a HUMAIN-approved session exporter. All you need is a H
 ## Quick Start
 
 ```bash
-npm install -g --ignore-scripts @humain/terminal
+npm install -g --ignore-scripts @earendil-works/pi-coding-agent
 ```
 
-`--ignore-scripts` disables dependency lifecycle scripts during install. HUMAIN Terminal does not require install scripts for normal npm installs.
+`--ignore-scripts` disables dependency lifecycle scripts during install. Pi does not require install scripts for normal npm installs.
+
+Installer alternative:
+
+```bash
+curl -fsSL https://pi.dev/install.sh | sh
+```
 
 Authenticate with an API key:
 
 ```bash
 export ANTHROPIC_API_KEY=sk-ant-...
-humain-terminal
+pi
 ```
 
 Or use your existing subscription:
 
 ```bash
-humain-terminal
+pi
 /login  # Then select provider
 ```
 
-Then just talk to HUMAIN Terminal. By default, it gives the model four tools: `read`, `write`, `edit`, and `bash`. The model uses these to fulfill your requests. Add capabilities via [skills](#skills), [prompt templates](#prompt-templates), [extensions](#extensions), or [packages](#packages).
+Then just talk to pi. By default, pi gives the model four tools: `read`, `write`, `edit`, and `bash`. The model uses these to fulfill your requests. Add capabilities via [skills](#skills), [prompt templates](#prompt-templates), [extensions](#extensions), or [pi packages](#pi-packages).
 
 **Platform notes:** [Windows](docs/windows.md) | [Termux (Android)](docs/termux.md) | [tmux](docs/tmux.md) | [Terminal setup](docs/terminal-setup.md) | [Shell aliases](docs/shell-aliases.md)
 
@@ -80,7 +96,7 @@ Then just talk to HUMAIN Terminal. By default, it gives the model four tools: `r
 
 ## Providers & Models
 
-For each built-in provider, HUMAIN Terminal maintains a list of tool-capable models. Configured provider catalogs refresh automatically; run `humain-terminal update --models` to force an immediate refresh. Authenticate via subscription (`/login`) or API key, then select any model from that provider via `/model` (or Ctrl+L).
+For each built-in provider, pi maintains a list of tool-capable models. Configured provider catalogs refresh automatically; run `pi update --models` to force an immediate refresh. Authenticate via subscription (`/login`) or API key, then select any model from that provider via `/model` (or Ctrl+L).
 
 **Subscriptions:**
 - Anthropic Claude Pro/Max
@@ -112,6 +128,7 @@ For each built-in provider, HUMAIN Terminal maintains a list of tool-capable mod
 - Hugging Face
 - Fireworks
 - Together AI
+- Baseten
 - Kimi For Coding
 - MiniMax
 - Xiaomi MiMo
@@ -123,7 +140,7 @@ Pi also supports the llama.cpp router server. Configure it with `/login llama.cp
 
 See [docs/providers.md](docs/providers.md) for other provider setup instructions.
 
-**Custom providers & models:** Add providers via `~/.humain-terminal/agent/models.json` if they speak a supported API (OpenAI, Anthropic, Google). For custom APIs or OAuth, use extensions. See [docs/models.md](docs/models.md) and [docs/custom-provider.md](docs/custom-provider.md).
+**Custom providers & models:** Add providers via `~/.pi/agent/models.json` if they speak a supported API (OpenAI, Anthropic, Google). For custom APIs or OAuth, use extensions. See [docs/models.md](docs/models.md) and [docs/custom-provider.md](docs/custom-provider.md).
 
 ---
 
@@ -180,11 +197,11 @@ Type `/` in the editor to trigger commands. [Extensions](#extensions) can regist
 | `/reload` | Reload keybindings, extensions, skills, prompts, themes, and context files |
 | `/hotkeys` | Show all keyboard shortcuts |
 | `/changelog` | Display version history |
-| `/quit` | Quit HUMAIN Terminal |
+| `/quit` | Quit pi |
 
 ### Keyboard Shortcuts
 
-See `/hotkeys` for the full list. Customize via `~/.humain-terminal/agent/keybindings.json`. See [docs/keybindings.md](docs/keybindings.md).
+See `/hotkeys` for the full list. Customize via `~/.pi/agent/keybindings.json`. See [docs/keybindings.md](docs/keybindings.md).
 
 **Commonly used:**
 
@@ -210,7 +227,7 @@ Submit messages while the agent is working:
 - **Escape** aborts and restores queued messages to editor
 - **Alt+Up** retrieves queued messages back to editor
 
-On Windows Terminal, `Alt+Enter` is fullscreen by default. Remap it in [docs/terminal-setup.md](docs/terminal-setup.md) so HUMAIN Terminal can receive the follow-up shortcut.
+On Windows Terminal, `Alt+Enter` is fullscreen by default. Remap it in [docs/terminal-setup.md](docs/terminal-setup.md) so pi can receive the follow-up shortcut.
 
 Configure delivery in [settings](docs/settings.md): `steeringMode` and `followUpMode` can be `"one-at-a-time"` (default, waits for response) or `"all"` (delivers all queued at once). `transport` selects provider transport preference (`"sse"`, `"websocket"`, or `"auto"`) for providers that support multiple transports.
 
@@ -222,15 +239,15 @@ Sessions are stored as JSONL files with a tree structure. Each entry has an `id`
 
 ### Management
 
-Sessions auto-save to `~/.humain-terminal/agent/sessions/` organized by working directory.
+Sessions auto-save to `~/.pi/agent/sessions/` organized by working directory.
 
 ```bash
-humain-terminal -c                  # Continue most recent session
-humain-terminal -r                  # Browse and select from past sessions
-humain-terminal --no-session        # Ephemeral mode (don't save)
-humain-terminal --name "my task"    # Set session display name at startup
-humain-terminal --session <path|id> # Use specific session file or ID
-humain-terminal --fork <path|id>    # Fork specific session file or ID into a new session
+pi -c                  # Continue most recent session
+pi -r                  # Browse and select from past sessions
+pi --no-session        # Ephemeral mode (don't save)
+pi --name "my task"    # Set session display name at startup
+pi --session <path|id> # Use specific session file or ID
+pi --fork <path|id>    # Fork specific session file or ID into a new session
 ```
 
 Use `/session` in interactive mode to see the current session ID before reusing it with `--session <id>` or `--fork <id>`.
@@ -270,50 +287,52 @@ Use `/settings` to modify common options, or edit JSON files directly:
 
 | Location | Scope |
 |----------|-------|
-| `~/.humain-terminal/agent/settings.json` | Global (all projects) |
-| `.humain-terminal/settings.json` | Project (overrides global) |
+| `~/.pi/agent/settings.json` | Global (all projects) |
+| `.pi/settings.json` | Project (overrides global) |
 
 See [docs/settings.md](docs/settings.md) for all options.
 
 ### Project Trust
 
-On interactive startup, HUMAIN Terminal asks before trusting a project folder that contains project-local settings, resources, or project `.agents/skills` and has no saved decision for the folder or a parent folder in `~/.humain-terminal/agent/trust.json`. Trusting a project allows HUMAIN Terminal to load `.humain-terminal/settings.json` and `.humain-terminal` resources, install missing project packages, and execute project extensions.
+On interactive startup, pi asks before trusting a project folder that contains project-local settings, resources, or project `.agents/skills` and has no saved decision for the folder or a parent folder in `~/.pi/agent/trust.json`. Trusting a project allows pi to load `.pi/settings.json` and `.pi` resources, install missing project packages, and execute project extensions.
 
-Before the trust decision, HUMAIN Terminal loads only context files, user/global extensions, and CLI `-e` extensions so they can handle the `project_trust` event. Project-local extensions, project package-managed extensions, and project settings are loaded only after the project is trusted. This split also applies when switching to a session from a different cwd whose trust has not been resolved in the current process.
+Before the trust decision, pi loads only context files, user/global extensions, and CLI `-e` extensions so they can handle the `project_trust` event. Project-local extensions, project package-managed extensions, and project settings are loaded only after the project is trusted. This split also applies when switching to a session from a different cwd whose trust has not been resolved in the current process.
 
 Non-interactive modes (`-p`, `--mode json`, and `--mode rpc`) do not show a trust prompt. Without an applicable saved trust decision, they use `defaultProjectTrust` from global settings: `ask` (default) and `never` ignore those project resources, while `always` trusts them. Pass `--approve`/`-a` or `--no-approve`/`-na` to override project trust for one run.
 
-If no extension or saved decision applies, `defaultProjectTrust` controls the fallback behavior. Set it to `"ask"`, `"always"`, or `"never"` in `~/.humain-terminal/agent/settings.json`, or change it with `/settings`.
+If no extension or saved decision applies, `defaultProjectTrust` controls the fallback behavior. Set it to `"ask"`, `"always"`, or `"never"` in `~/.pi/agent/settings.json`, or change it with `/settings`.
 
-`humain-terminal config` and package commands use the same project trust flow, except `humain-terminal update` never prompts. Pass `--approve` to trust project-local settings for one command or `--no-approve` to ignore them.
+`pi config` and package commands use the same project trust flow, except `pi update` never prompts. Pass `--approve` to trust project-local settings for one command or `--no-approve` to ignore them.
 
-Use `/trust` in interactive mode to save a project trust decision for future sessions, including trust for the immediate parent folder. It writes `~/.humain-terminal/agent/trust.json` only; the current session is not reloaded, so restart HUMAIN Terminal for changes to take effect.
+Use `/trust` in interactive mode to save a project trust decision for future sessions, including trust for the immediate parent folder. It writes `~/.pi/agent/trust.json` only; the current session is not reloaded, so restart pi for changes to take effect.
 
 ### Telemetry and update checks
 
-HUMAIN Terminal has two separate startup features:
+Pi has two separate startup features:
 
-- **Update check:** fetches the configured HUMAIN Terminal release endpoint to check whether a newer version exists. Disable it with `HUMAIN_TERMINAL_SKIP_VERSION_CHECK=1`. Disabling update checks only turns off this check.
-- **Install/update telemetry:** after first install or a changelog-detected update, sends an anonymous version ping to the configured HUMAIN Terminal telemetry endpoint. This setting also controls optional provider attribution headers for OpenRouter, Cloudflare, and direct NVIDIA NIM requests. Opt out by setting `enableInstallTelemetry` to `false` in `settings.json`, or by setting `HUMAIN_TERMINAL_TELEMETRY=0`. This does not disable update checks; HUMAIN Terminal may still contact the release endpoint for the latest version unless update checks are disabled or offline mode is enabled.
+- **Update check:** fetches `https://pi.dev/api/latest-version` to check whether a newer Pi version exists. Disable it with `PI_SKIP_VERSION_CHECK=1`. Disabling update checks only turns off this check.
+- **Install/update telemetry:** after first install or a changelog-detected update, sends an anonymous version ping to `https://pi.dev/api/report-install`. This setting also controls optional provider attribution headers for OpenRouter, Cloudflare, and direct NVIDIA NIM requests. Opt out by setting `enableInstallTelemetry` to `false` in `settings.json`, or by setting `PI_TELEMETRY=0`. This does not disable update checks; Pi may still contact `pi.dev` for the latest version unless update checks are disabled or offline mode is enabled.
 
-Use `--offline` or `HUMAIN_TERMINAL_OFFLINE=1` to disable all startup network operations described here, including update checks, package update checks, and install/update telemetry.
+Use `--offline` or `PI_OFFLINE=1` to disable all startup network operations described here, including update checks, package update checks, and install/update telemetry.
 
 ---
 
 ## Context Files
 
-HUMAIN Terminal loads `AGENTS.md` (or `CLAUDE.md`) at startup from:
-- `~/.humain-terminal/agent/AGENTS.md` (global)
+Pi loads `AGENTS.md` (or `CLAUDE.md`) at startup from:
+- `~/.pi/agent/AGENTS.md` (global)
 - Parent directories (walking up from cwd)
 - Current directory
 
+If a directory contains `AGENTS.override.md`, Pi loads it instead of `AGENTS.md` or `CLAUDE.md` from that directory. Context files from other directories are still concatenated.
+
 Use for project instructions (`AGENTS.md`/`CLAUDE.md`), conventions, common commands. All matching files are concatenated.
 
 Disable context file loading with `--no-context-files` (or `-nc`).
 
 ### System Prompt
 
-Replace the default system prompt with `.humain-terminal/SYSTEM.md` (project) or `~/.humain-terminal/agent/SYSTEM.md` (global). Append without replacing via `APPEND_SYSTEM.md`.
+Replace the default system prompt with `.pi/SYSTEM.md` (project) or `~/.pi/agent/SYSTEM.md` (global). Append without replacing via `APPEND_SYSTEM.md`.
 
 ---
 
@@ -324,19 +343,19 @@ Replace the default system prompt with `.humain-terminal/SYSTEM.md` (project) or
 Reusable prompts as Markdown files. Type `/name` to expand.
 
 ```markdown
-<!-- ~/.humain-terminal/agent/prompts/review.md -->
+<!-- ~/.pi/agent/prompts/review.md -->
 Review this code for bugs, security issues, and performance problems.
 Focus on: {{focus}}
 ```
 
-Place in `~/.humain-terminal/agent/prompts/`, `.humain-terminal/prompts/`, or a [package](#packages) to share with others. See [docs/prompt-templates.md](docs/prompt-templates.md).
+Place in `~/.pi/agent/prompts/`, `.pi/prompts/`, or a [pi package](#pi-packages) to share with others. See [docs/prompt-templates.md](docs/prompt-templates.md).
 
 ### Skills
 
 On-demand capability packages following the [Agent Skills standard](https://agentskills.io). Invoke via `/skill:name` or let the agent load them automatically.
 
 ```markdown
-<!-- ~/.humain-terminal/agent/skills/my-skill/SKILL.md -->
+<!-- ~/.pi/agent/skills/my-skill/SKILL.md -->
 # My Skill
 Use this skill when the user asks about X.
 
@@ -345,23 +364,23 @@ Use this skill when the user asks about X.
 2. Then that
 ```
 
-Place in `~/.humain-terminal/agent/skills/`, `~/.agents/skills/`, `.humain-terminal/skills/`, or `.agents/skills/` (from `cwd` up through parent directories) or a [package](#packages) to share with others. See [docs/skills.md](docs/skills.md).
+Place in `~/.pi/agent/skills/`, `~/.agents/skills/`, `.pi/skills/`, or `.agents/skills/` (from `cwd` up through parent directories) or a [pi package](#pi-packages) to share with others. See [docs/skills.md](docs/skills.md).
 
 ### Extensions
 
 <p align="center"><img src="docs/images/doom-extension.png" alt="Doom Extension" width="600"></p>
 
-TypeScript modules that extend HUMAIN Terminal with custom tools, commands, keyboard shortcuts, event handlers, and UI components.
+TypeScript modules that extend pi with custom tools, commands, keyboard shortcuts, event handlers, and UI components.
 
 ```typescript
-export default function (terminal: ExtensionAPI) {
-  terminal.registerTool({ name: "deploy", ... });
-  terminal.registerCommand("stats", { ... });
-  terminal.on("tool_call", async (event, ctx) => { ... });
+export default function (pi: ExtensionAPI) {
+  pi.registerTool({ name: "deploy", ... });
+  pi.registerCommand("stats", { ... });
+  pi.on("tool_call", async (event, ctx) => { ... });
 }
 ```
 
-The default export can also be `async`. HUMAIN Terminal waits for async extension factories before startup continues, which is useful for one-time initialization such as fetching remote model lists before calling `terminal.registerProvider()`.
+The default export can also be `async`. pi waits for async extension factories before startup continues, which is useful for one-time initialization such as fetching remote model lists before calling `pi.registerProvider()`.
 
 **What's possible:**
 - Custom tools (or replace built-in tools entirely)
@@ -373,23 +392,23 @@ The default export can also be `async`. HUMAIN Terminal waits for async extensio
 - Git checkpointing and auto-commit
 - SSH and sandbox execution
 - MCP server integration
-- Match another coding-terminal workflow
+- Make pi look like Claude Code
 - Games while waiting (yes, Doom runs)
 - ...anything you can dream up
 
-Place in `~/.humain-terminal/agent/extensions/`, `.humain-terminal/extensions/`, or a [package](#packages) to share with others. See [docs/extensions.md](docs/extensions.md) and [examples/extensions/](examples/extensions/).
+Place in `~/.pi/agent/extensions/`, `.pi/extensions/`, or a [pi package](#pi-packages) to share with others. See [docs/extensions.md](docs/extensions.md) and [examples/extensions/](examples/extensions/).
 
 ### Themes
 
-Built-in: `humain-dark`, `humain-light`, `dark`, `light`. Themes hot-reload: modify the active theme file and HUMAIN Terminal immediately applies changes.
+Built-in: `dark`, `light`. Themes hot-reload: modify the active theme file and pi immediately applies changes.
 
-Place in `~/.humain-terminal/agent/themes/`, `.humain-terminal/themes/`, or a [package](#packages) to share with others. See [docs/themes.md](docs/themes.md).
+Place in `~/.pi/agent/themes/`, `.pi/themes/`, or a [pi package](#pi-packages) to share with others. See [docs/themes.md](docs/themes.md).
 
-### Packages
+### Pi Packages
 
-Bundle and share extensions, skills, prompts, and themes via npm or git.
+Bundle and share extensions, skills, prompts, and themes via npm or git. Find packages on [npmjs.com](https://www.npmjs.com/search?q=keywords%3Api-package) or [Discord](https://discord.com/channels/1456806362351669492/1457744485428629628).
 
-> **Security:** HUMAIN Terminal packages run with full system access. Extensions execute arbitrary code, and skills can instruct the model to perform any action including running executables. Review source code before installing third-party packages.
+> **Security:** Pi packages run with full system access. Extensions execute arbitrary code, and skills can instruct the model to perform any action including running executables. Review source code before installing third-party packages.
 
 ```bash
 pi install npm:@foo/pi-tools
@@ -405,25 +424,25 @@ pi install ssh://git@github.com/user/repo@v1    # tag or commit
 pi remove npm:@foo/pi-tools
 pi uninstall npm:@foo/pi-tools          # alias for remove
 pi list
-humain-terminal update                               # update HUMAIN Terminal only
-humain-terminal update --all                         # update HUMAIN Terminal and packages
-humain-terminal update --extensions                  # update packages only
-humain-terminal update --models                      # refresh model catalogs only
-humain-terminal update --self                        # update HUMAIN Terminal only
-humain-terminal update --self --force                # reinstall HUMAIN Terminal even if current
-humain-terminal update npm:@foo/pi-tools             # update one package
+pi update                               # update pi only
+pi update --all                         # update pi and packages
+pi update --extensions                  # update packages only
+pi update --models                      # refresh model catalogs only
+pi update --self                        # update pi only
+pi update --self --force                # reinstall pi even if current
+pi update npm:@foo/pi-tools             # update one package
 pi config                               # enable/disable extensions, skills, prompts, themes
 ```
 
-Packages install to `~/.humain-terminal/agent/git/` (git) or `~/.humain-terminal/agent/npm/` (npm). Use `-l` for project-local installs (`.humain-terminal/git/`, `.humain-terminal/npm/`). Git `@ref` values are pinned tags or commits; pinned packages are skipped by `humain-terminal update --extensions` and `humain-terminal update --all`, so use `humain-terminal install git:host/user/repo@new-ref` to move an existing package to a new ref. Git packages install dependencies with `npm install --omit=dev` by default, so runtime deps must be listed under `dependencies`; when `npmCommand` is configured, git packages use plain `install` for compatibility with wrappers. If you use a Node version manager and want package installs to reuse a stable npm context, set `npmCommand` in `settings.json`, for example `["mise", "exec", "node@20", "--", "npm"]`.
+Packages install to `~/.pi/agent/git/` (git) or `~/.pi/agent/npm/` (npm). Use `-l` for project-local installs (`.pi/git/`, `.pi/npm/`). Git `@ref` values are pinned tags or commits; pinned packages are skipped by `pi update --extensions` and `pi update --all`, so use `pi install git:host/user/repo@new-ref` to move an existing package to a new ref. Git packages install dependencies with `npm install --omit=dev` by default, so runtime deps must be listed under `dependencies`; when `npmCommand` is configured, git packages use plain `install` for compatibility with wrappers. If you use a Node version manager and want package installs to reuse a stable npm context, set `npmCommand` in `settings.json`, for example `["mise", "exec", "node@20", "--", "npm"]`.
 
-Create a package by adding a HUMAIN Terminal `humainTerminal` key to `package.json`:
+Create a package by adding a `pi` key to `package.json`:
 
 ```json
 {
-  "name": "my-humain-terminal-package",
-  "keywords": ["humain-terminal-package"],
-  "humainTerminal": {
+  "name": "my-pi-package",
+  "keywords": ["pi-package"],
+  "pi": {
     "extensions": ["./extensions"],
     "skills": ["./skills"],
     "prompts": ["./prompts"],
@@ -432,7 +451,7 @@ Create a package by adding a HUMAIN Terminal `humainTerminal` key to `package.js
 }
 ```
 
-Without a `humainTerminal` manifest, HUMAIN Terminal auto-discovers from conventional directories (`extensions/`, `skills/`, `prompts/`, `themes/`).
+Without a `pi` manifest, pi auto-discovers from conventional directories (`extensions/`, `skills/`, `prompts/`, `themes/`).
 
 See [docs/packages.md](docs/packages.md).
 
@@ -443,7 +462,7 @@ See [docs/packages.md](docs/packages.md).
 ### SDK
 
 ```typescript
-import { createAgentSession, ModelRuntime, SessionManager } from "@humain/terminal";
+import { createAgentSession, ModelRuntime, SessionManager } from "@earendil-works/pi-coding-agent";
 
 const modelRuntime = await ModelRuntime.create();
 const { session } = await createAgentSession({
@@ -463,7 +482,7 @@ See [docs/sdk.md](docs/sdk.md) and [examples/sdk/](examples/sdk/).
 For non-Node.js integrations, use RPC mode over stdin/stdout:
 
 ```bash
-humain-terminal --mode rpc
+pi --mode rpc
 ```
 
 RPC mode uses strict LF-delimited JSONL framing. Clients must split records on `\n` only. Do not use generic line readers like Node `readline`, which also split on Unicode separators inside JSON payloads.
@@ -474,11 +493,11 @@ See [docs/rpc.md](docs/rpc.md) for the protocol.
 
 ## Philosophy
 
-HUMAIN Terminal is aggressively extensible so it does not dictate your workflow. Features that other tools bake in can be built with [extensions](#extensions), [skills](#skills), or installed from third-party [packages](#packages). This keeps the core minimal while letting you shape HUMAIN Terminal to fit how you work.
+Pi is aggressively extensible so it doesn't have to dictate your workflow. Features that other tools bake in can be built with [extensions](#extensions), [skills](#skills), or installed from third-party [pi packages](#pi-packages). This keeps the core minimal while letting you shape pi to fit how you work.
 
 **No MCP.** Build CLI tools with READMEs (see [Skills](#skills)), or build an extension that adds MCP support. [Why?](https://mariozechner.at/posts/2025-11-02-what-if-you-dont-need-mcp/)
 
-**No sub-agents.** There's many ways to do this. Spawn HUMAIN Terminal instances via tmux, build your own with [extensions](#extensions), or install a package that does it your way.
+**No sub-agents.** There's many ways to do this. Spawn pi instances via tmux, or build your own with [extensions](#extensions), or install a package that does it your way.
 
 **No permission popups.** Run in a container, or build your own confirmation flow with [extensions](#extensions) inline with your environment and security requirements.
 
@@ -488,12 +507,14 @@ HUMAIN Terminal is aggressively extensible so it does not dictate your workflow.
 
 **No background bash.** Use tmux. Full observability, direct interaction.
 
+Read the [blog post](https://mariozechner.at/posts/2025-11-30-pi-coding-agent/) for the full rationale.
+
 ---
 
 ## CLI Reference
 
 ```bash
-humain-terminal [options] [@files...] [messages...]
+pi [options] [@files...] [messages...]
 ```
 
 ### Package Commands
@@ -502,18 +523,18 @@ humain-terminal [options] [@files...] [messages...]
 pi install <source> [-l]     # Install package, -l for project-local
 pi remove <source> [-l]      # Remove package
 pi uninstall <source> [-l]   # Alias for remove
-humain-terminal update [source|self|pi]   # Update pi only, or one package source
-humain-terminal update --all              # Update pi and packages
-humain-terminal update --extensions       # Update packages only
-humain-terminal update --models           # Refresh model catalogs only
-humain-terminal update --self             # Update pi only
-humain-terminal update --self --force     # Reinstall pi even if current
-humain-terminal update --extension <src>  # Update one package
+pi update [source|self|pi]   # Update pi only, or one package source
+pi update --all              # Update pi and packages
+pi update --extensions       # Update packages only
+pi update --models           # Refresh model catalogs only
+pi update --self             # Update pi only
+pi update --self --force     # Reinstall pi even if current
+pi update --extension <src>  # Update one package
 pi list                      # List installed packages
 pi config                    # Enable/disable package resources
 ```
 
-`humain-terminal config` and project package commands accept `--approve`/`--no-approve` to trust or ignore project-local settings for one command. `humain-terminal update` never prompts for project trust.
+`pi config` and project package commands accept `--approve`/`--no-approve` to trust or ignore project-local settings for one command. `pi update` never prompts for project trust.
 
 ### Modes
 
@@ -525,10 +546,10 @@ pi config                    # Enable/disable package resources
 | `--mode rpc` | RPC mode for process integration (see [docs/rpc.md](docs/rpc.md)) |
 | `--export <in> [out]` | Export session to HTML |
 
-In print mode, HUMAIN Terminal also reads piped stdin and merges it into the initial prompt:
+In print mode, pi also reads piped stdin and merges it into the initial prompt:
 
 ```bash
-cat README.md | humain-terminal -p "Summarize this text"
+cat README.md | pi -p "Summarize this text"
 ```
 
 ### Model Options
@@ -587,6 +608,7 @@ Combine `--no-*` with explicit flags to load exactly what you need, ignoring set
 |--------|-------------|
 | `--system-prompt <text>` | Replace default prompt (context files and skills still appended) |
 | `--append-system-prompt <text>` | Append to system prompt |
+| `--tui-mode <mode>` | TUI mode: `regular` (default) or experimental `fullscreen` |
 | `--verbose` | Force verbose startup |
 | `-a`, `--approve` | Trust project-local files for this run |
 | `-na`, `--no-approve` | Ignore project-local files for this run |
@@ -598,76 +620,72 @@ Combine `--no-*` with explicit flags to load exactly what you need, ignoring set
 Prefix files with `@` to include in the message:
 
 ```bash
-humain-terminal @prompt.md "Answer this"
-humain-terminal -p @screenshot.png "What's in this image?"
-humain-terminal @code.ts @test.ts "Review these files"
+pi @prompt.md "Answer this"
+pi -p @screenshot.png "What's in this image?"
+pi @code.ts @test.ts "Review these files"
 ```
 
 ### Examples
 
 ```bash
 # Interactive with initial prompt
-humain-terminal "List all .ts files in src/"
+pi "List all .ts files in src/"
 
 # Non-interactive
-humain-terminal -p "Summarize this codebase"
+pi -p "Summarize this codebase"
 
 # Non-interactive with piped stdin
-cat README.md | humain-terminal -p "Summarize this text"
+cat README.md | pi -p "Summarize this text"
 
 # Named one-shot session
-humain-terminal --name "release audit" -p "Audit this repository"
+pi --name "release audit" -p "Audit this repository"
 
 # Different model
-humain-terminal --provider openai --model gpt-4o "Help me refactor"
+pi --provider openai --model gpt-4o "Help me refactor"
 
 # Model with provider prefix (no --provider needed)
-humain-terminal --model openai/gpt-4o "Help me refactor"
+pi --model openai/gpt-4o "Help me refactor"
 
 # Model with thinking level shorthand
-humain-terminal --model sonnet:high "Solve this complex problem"
+pi --model sonnet:high "Solve this complex problem"
 
 # Limit model cycling
-humain-terminal --models "claude-*,gpt-4o"
+pi --models "claude-*,gpt-4o"
 
 # Read-only mode
-humain-terminal --tools read,grep,find,ls -p "Review the code"
+pi --tools read,grep,find,ls -p "Review the code"
 
 # Disable one extension or built-in tool while keeping the rest available
-humain-terminal --exclude-tools ask_question
+pi --exclude-tools ask_question
 
 # High thinking level
-humain-terminal --thinking high "Solve this complex problem"
+pi --thinking high "Solve this complex problem"
 ```
 
 ### Environment Variables
 
 | Variable | Description |
 |----------|-------------|
-| `HUMAIN_TERMINAL_CODING_AGENT` | Set to `true` by the CLI and RPC entry points so child processes can detect that they run inside HUMAIN Terminal |
-| `HUMAIN_TERMINAL_CODING_AGENT_DIR` | Override config directory (default: `~/.humain-terminal/agent`) |
-| `HUMAIN_TERMINAL_CODING_AGENT_SESSION_DIR` | Override session storage directory (overridden by `--session-dir`) |
-| `HUMAIN_TERMINAL_PACKAGE_DIR` | Override package directory (useful for Nix/Guix where store paths tokenize poorly) |
-| `HUMAIN_TERMINAL_OFFLINE` | Disable startup network operations, including update checks, package update checks, and install/update telemetry |
-| `HUMAIN_TERMINAL_SKIP_VERSION_CHECK` | Skip the HUMAIN Terminal version check at startup. This prevents the configured latest-version request |
-| `HUMAIN_TERMINAL_VERSION_CHECK_URL` | Override the latest-version endpoint |
-| `HUMAIN_TERMINAL_TELEMETRY` | Override install/update telemetry and provider attribution headers. Use `1`/`true`/`yes` to enable or `0`/`false`/`no` to disable. This does not disable update checks |
-| `HUMAIN_TERMINAL_INSTALL_TELEMETRY_URL` | Override the install/update telemetry endpoint |
-| `HUMAIN_TERMINAL_CHANGELOG_URL` | Override the release changelog URL |
-| `HUMAIN_TERMINAL_BINARY_RELEASE_URL` | Override the binary self-update fallback URL |
-| `HUMAIN_TERMINAL_SHARE_VIEWER_URL` | Override the `/share` viewer base URL |
-| `HUMAIN_TERMINAL_CACHE_RETENTION` | Set to `long` for extended prompt cache (Anthropic: 1h, OpenAI: 24h) |
+| `AI_AGENT` | Set to `pi` by the CLI and RPC entry points so generic tooling can attribute child processes to Pi |
+| `PI_CODING_AGENT` | Set to `true` by the CLI and RPC entry points so child processes can detect that they run inside Pi |
+| `PI_CODING_AGENT_DIR` | Override config directory (default: `~/.pi/agent`) |
+| `PI_CODING_AGENT_SESSION_DIR` | Override session storage directory (overridden by `--session-dir`) |
+| `PI_PACKAGE_DIR` | Override package directory (useful for Nix/Guix where store paths tokenize poorly) |
+| `PI_OFFLINE` | Disable startup network operations, including update checks, package update checks, and install/update telemetry |
+| `PI_SKIP_VERSION_CHECK` | Skip the Pi version update check at startup. This prevents the `pi.dev` latest-version request |
+| `PI_TELEMETRY` | Override install/update telemetry and provider attribution headers. Use `1`/`true`/`yes` to enable or `0`/`false`/`no` to disable. This does not disable update checks |
+| `PI_CACHE_RETENTION` | Set to `long` for extended prompt cache (Anthropic: 1h, OpenAI: 24h) |
 | `VISUAL`, `EDITOR` | Fallback external editor for Ctrl+G when `externalEditor` is unset; defaults to Notepad on Windows and `nano` elsewhere |
 
 Commands run by the LLM-callable bash tool also receive current session metadata:
 
 | Variable | Description |
 |----------|-------------|
-| `HUMAIN_TERMINAL_SESSION_ID` | Current session ID |
-| `HUMAIN_TERMINAL_SESSION_FILE` | Absolute session JSONL path; unset for ephemeral sessions |
-| `HUMAIN_TERMINAL_PROVIDER` | Currently selected model provider |
-| `HUMAIN_TERMINAL_MODEL` | Currently selected model ID |
-| `HUMAIN_TERMINAL_REASONING_LEVEL` | Current effective reasoning level |
+| `PI_SESSION_ID` | Current session ID |
+| `PI_SESSION_FILE` | Absolute session JSONL path; unset for ephemeral sessions |
+| `PI_PROVIDER` | Currently selected model provider |
+| `PI_MODEL` | Currently selected model ID |
+| `PI_REASONING_LEVEL` | Current effective reasoning level |
 
 These values are resolved when each command starts. See [Environment Variables](docs/environment-variables.md#bash-tool-session-environment) for semantics, examples, and custom-tool opt-out.
 
@@ -683,6 +701,12 @@ MIT
 
 ## See Also
 
-- [docs/index.md](docs/index.md): HUMAIN Terminal documentation
-- [docs/development.md](docs/development.md): local development and debugging
-- [examples/](examples/): extension and SDK examples
+- [@earendil-works/pi-ai](https://www.npmjs.com/package/@earendil-works/pi-ai): Core LLM toolkit
+- [@earendil-works/pi-agent-core](https://www.npmjs.com/package/@earendil-works/pi-agent-core): Agent framework
+- [@earendil-works/pi-tui](https://www.npmjs.com/package/@earendil-works/pi-tui): Terminal UI components
+
+<p align="center">
+  <a href="https://pi.dev">pi.dev</a> domain graciously donated by
+  <br /><br />
+  <a href="https://exe.dev"><img src="docs/images/exy.png" alt="Exy mascot" width="48" /><br />exe.dev</a>
+</p>

package/dist/cli/args.d.ts

@@ -3,8 +3,10 @@
  */
 import type { ThinkingLevel } from "@earendil-works/pi-agent-core";
 import type { ExtensionFlag } from "../core/extensions/types.ts";
-export type Mode = "text" | "json" | "rpc";
+import type { TuiMode } from "../core/settings-manager.ts";
+export type Mode = "text" | "json" | "rpc" | "agent-exec";
 export interface Args {
+    cwd?: string;
     provider?: string;
     model?: string;
     apiKey?: string;
@@ -21,7 +23,6 @@ export interface Args {
     session?: string;
     sessionId?: string;
     fork?: string;
-    cwd?: string;
     sessionDir?: string;
     models?: string[];
     tools?: string[];
@@ -41,6 +42,7 @@ export interface Args {
     noContextFiles?: boolean;
     listModels?: string | true;
     offline?: boolean;
+    tuiMode?: TuiMode;
     verbose?: boolean;
     projectTrustOverride?: boolean;
     messages: string[];