Getting startedDesktop v26.8.1Beginner-friendly · about 20 minutes

PAUITerm operator's guide

From first install to a working workspace.

This guide explains what PAUITerm needs, what it does not need, and how to use every core Desktop feature in the right order. Follow it with an existing codebase or an empty local folder.

Your finish line

One project open with a working shell, an optional AI agent, a reusable command, and files ready in the editor.

01
Readiness

Know what you need before you install

PAUITerm is a desktop application, not a Node package. Most developer tools are conditional: install only the tools your project and chosen agents actually use.

PAUITerm Desktop
Required

The application itself. Use the installer that matches your operating system and CPU architecture.

A local folder
Required

An existing project or an empty folder. It does not need to be a Git repository.

Node.js + npm
Conditional

Needed for Node-based projects and npm-installed CLIs such as Codex or Gemini. Not needed just to run PAUITerm.

Claude, Codex, Gemini, or another AI CLI
Conditional

Needed only for Agents. PAUITerm stores the launch configuration; it does not install or pay for an AI provider.

Git or a GitHub account
Optional

Git is strongly recommended for safe version history. GitHub is not required for projects, terminals, commands, or the editor.

VS Code
Optional

The built-in PAUITerm Editor works without VS Code. Install it only for the external VS Code workflows.

Rust, Cargo, or Tauri
Not needed

End users do not need the PAUITerm development toolchain. These are only for building PAUITerm from source.

02
Application

Install PAUITerm Desktop

Download the installer from the official PAUITerm site. Do not use an installer for a different operating system or CPU architecture.

  1. 1

    Open the Downloads page

    Go to the official PAUITerm Downloads page and confirm the current version.
  2. 2

    Choose the correct build

    On macOS, choose Apple Silicon for M-series Macs or Intel for Intel Macs. If you are unsure, run the command below: arm64 means Apple Silicon and x86_64 means Intel.
    macOS Terminal
    uname -m
  3. 3

    Install and launch

    Open the downloaded .dmg, move PAUITerm to Applications, then launch it. Windows and Linux builds marked Coming Soon are not downloadable yet; do not substitute the macOS installer.
  4. 4

    Approve only the official build

    If macOS blocks the first launch, open System Settings → Privacy & Security and use Open Anyway only after confirming the file came from the official PAUITerm download page.
03
Prerequisites

Install only the developer tools you will use

Do this in your normal system terminal before adding an agent in PAUITerm. Each executable must be installed, available in PATH, and authenticated.

A

Node.js and npm

Install when your project uses JavaScript or TypeScript, when a command starts with npm or npx, or when an AI CLI uses npm installation.

Verify
node --version
npm --version
Install a current LTS release. npm is included with Node.js, so do not install npm separately in the normal setup. Restart your terminal and PAUITerm after installation.
Node.js official download
B

OpenAI Codex CLI

Install only if you want a Codex agent. The standard npm installation requires Node.js and npm.

Install
npm install -g @openai/codex
Verify
codex --version
Run codex once in your system terminal and complete sign-in. Codex supports ChatGPT sign-in or API-key authentication. Confirm the login before starting it from PAUITerm.
Official Codex CLI guide
C

Claude Code

Install only if you want a Claude Code agent. The recommended native installer does not require Node.js.

Install
curl -fsSL https://claude.ai/install.sh | bash
Verify
claude --version
claude doctor
The install command above is for macOS, Linux, and WSL. On Windows PowerShell, use irm https://claude.ai/install.ps1 | iex. Then run claude and authenticate with an eligible account. An npm method also exists, but the native installer is the current recommended path.
Official Claude Code setup
D

Gemini CLI

Install only if you want a Gemini agent. Its npm installation requires Node.js and npm.

Install
npm install -g @google/gemini-cli
Verify
gemini --version
Run gemini once and choose a supported authentication method, commonly Sign in with Google. Finish that flow outside PAUITerm first.
Official Gemini CLI repository
E

Ollama

Install when you want to run a model locally. Ollama does not require Node.js, npm, or a cloud-provider API key for downloaded local models.

Verify
ollama --version
Download the official Ollama application on macOS or Windows. On Linux, use the official install script below. Model downloads require internet access and additional disk space; local performance depends on the model size and your available RAM or VRAM.
Linux install
curl -fsSL https://ollama.com/install.sh | sh
Download and test the same model used by PAUITerm's default Ollama template before adding the agent:
Download and test a model
ollama pull llama3
ollama run llama3

You can use Qwen, Gemma 4, and other Ollama models

PAUITerm is not limited to Llama 3. Download any compatible model from the Ollama library, test it in your system terminal, and use its exact tag in the PAUITerm Agent arguments. For Qwen, use the current qwen3 tag.

Example model downloads
ollama pull qwen3
ollama pull gemma4
ollama pull gemma3:4b
ollama pull deepseek-r1:8b

Choose a smaller variant when RAM, VRAM, or disk space is limited. Model names and variants are case-sensitive tags; copy the exact tag from the official Ollama model library.

After the model is downloaded, a local run can work without a cloud AI subscription. Keep the Ollama application or service running while the PAUITerm agent is active.
Official Ollama quickstart
04
Preflight

Verify everything before opening an agent

A version number means the executable is visible. A command-not-found message means the tool is missing or PAUITerm cannot see its PATH yet.

macOS / Linux

zsh, bash, or fish
command -v node npm codex claude gemini ollama
node --version
npm --version

Windows PowerShell

PowerShell
Get-Command node,npm,codex,claude,gemini,ollama -ErrorAction SilentlyContinue
node --version
npm --version

Optional tools may be absent. Verify only what you plan to use. After a new global installation, fully quit and reopen PAUITerm so the desktop process can rebuild its executable search path.

05
First workspace

Create your first project

In PAUITerm, a project is a saved connection to a local folder. The folder remains the source of truth; PAUITerm does not upload or copy it.

  1. 1

    Click + Add Project

    Use the orange + button at the bottom of the project rail.
  2. 2

    Choose the folder

    Select Browse… and pick an existing codebase or empty folder. The project name fills from the folder name and can be changed.
  3. 3

    Set the identity

    Add a short badge of up to four characters and choose an accent color. These make projects easy to recognize in the left rail.
  4. 4

    Choose an editor engine

    Select PAUITerm Editor for the built-in Monaco editor. Choose Local VS Code Web only if OpenVSCode Server, code-server, or a compatible VS Code web provider is already available locally.
  5. 5

    Create Project

    PAUITerm opens the project and starts watching its files. Nothing is initialized in Git and no GitHub login is requested.
06
Orientation

Learn the workspace before you run anything

The interface separates saved items from live panes. Closing a pane hides that view; stopping a session ends its process.

Project rail

Switch projects from the badge tiles. Use the + button to add another local folder.

Project sidebar

Expand Agents, Terminals, Commands, and Settings. Hover a row for lifecycle controls.

Workspace panes

Keep the editor and live sessions visible together. PAUITerm arranges up to six panes with draggable dividers.

Editor explorer

Browse the folder tree, open files, and create, rename, move, duplicate, or delete items.

Status and controls

Running
Idle / waiting
Stopped
▶ Start / Run↺ Restart■ Stop✎ Edit× Delete
07
Live shell

Open and use a terminal

A terminal is an interactive shell that starts in the project folder. Use it exactly as you use Terminal, PowerShell, or another system shell.

  1. 1

    Create a terminal

    Click the + beside Terminals. PAUITerm opens the default shell in a workspace pane.
  2. 2

    Run project commands

    Install dependencies, run tests, or start the app. The tool behind each command must already be installed.
    Example Node project
    npm install
    npm run dev
  3. 3

    Use a different shell when needed

    Use the + shell selector. PAUITerm detects common shells including zsh, bash, fish, PowerShell, Command Prompt, WSL, and Git Bash when available.
  4. 4

    Manage the lifecycle

    Use Start, Restart, or Stop. Right-click a terminal row for rename and delete actions.
08
AI sessions

Add and run an AI agent

An agent is a saved CLI launch configuration. PAUITerm runs the real CLI in a PTY; the provider still owns authentication, billing, models, and usage limits.

  1. 1

    Test the CLI outside PAUITerm

    Run codex, claude, gemini, or an Ollama command such as ollama run qwen3 or ollama run gemma4 in your system terminal first. Finish authentication for cloud CLIs or confirm the selected local Ollama model responds.
  2. 2

    Click + Add Agent

    In the project sidebar, open Agents and click its + action.
  3. 3

    Choose a template

    Select an installed CLI and confirm its Executable: codex, claude, gemini, or ollama.
  4. 4

    Keep arguments intentional

    Leave Arguments empty for a normal first run. Add flags only when you understand the current CLI documentation. Avoid permission-bypass flags as a default.
  5. 5

    Choose shell and lifecycle options

    Auto is correct for most users. Start after save launches immediately. Auto-restart should be reserved for sessions that must return after an unexpected exit.
  6. 6

    Save and work in the pane

    Give the agent a focused task, review its proposed changes, and use the sidebar controls to stop or restart it.
Ollama template in PAUITerm
ExecutableollamaArgumentsrun llama3ShellAuto (system default)

Replace llama3 with the exact name of another downloaded model. Examples: use run qwen3, run gemma4, run gemma3:4b, or run deepseek-r1:8b in the Arguments field. The model must already be downloaded and the Ollama service must be running. ollama run provides an interactive model chat. For agentic file editing and command tools, first test a coding-agent integration such as ollama launch codex --model qwen3, ollama launch claude --model gemma4, or ollama launch opencode --model gemma4 in your system terminal, then save the working launch configuration as a custom PAUITerm agent.

09
Repeatable work

Save commands you run often

A saved command turns a long or frequently used shell line into a named project action with its own live output pane.

Name
A short action name, such as Dev server or Run tests.
Description
Optional context for teammates or your future self.
Command
The exact shell line to execute, such as npm run dev.
Shell
Use Auto unless the command depends on PowerShell, WSL, bash, or another shell.
Working Directory
Defaults to the project folder. Browse only when it must start elsewhere.
Start after save
Runs the command immediately after creation.
Auto-restart on exit
Useful for dev servers and workers; leave off for tests and other one-time commands.
Long-running
npm run dev
Auto-restart can be helpful.
One-time
npm test
Leave auto-restart off.
Docker Compose
docker compose up
Requires Docker Desktop or Engine.
Laravel
php artisan serve
Requires PHP and project dependencies.

The Command field suggests entries from the offline catalog and scripts discovered in package.json, composer.json, Makefile, and justfile. A suggestion does not install the underlying program.

10
Files

Edit and manage project files

The built-in PAUITerm Editor uses Monaco, the editing engine behind VS Code, with a project file tree and multi-file tabs.

  • Open a file from Explorer; it appears in an editor tab.
  • Create a file or folder from the toolbar or context menu.
  • Right-click to cut, copy, paste, duplicate, rename, move, or delete.
  • Use the file filter or Quick Open to find files quickly.
  • Watch the tab dot for unsaved changes; PAUITerm also auto-saves.
  • For outside changes, choose Revert or Overwrite from the banner.

Useful shortcuts

⌘/Ctrl + PQuick Open a file
⌘/Ctrl + SSave the active file
⌘/Ctrl + NCreate a new file
⌘/Ctrl + Shift + NCreate a new folder
⌘/Ctrl + WClose the active editor tab
⌘/Ctrl + BacktickShow or hide the active terminal pane
Ctrl + TabMove between editor tabs
11
End-to-end

Complete your first daily workflow

This is the shortest practical loop that exercises every core PAUITerm area without adding unnecessary tools.

/01

Open the project

Select its badge from the project rail.

/02

Start a terminal

Install dependencies or inspect the project.

/03

Start the dev command

Run a saved command such as npm run dev.

/04

Open the editor

Change a file and save it.

/05

Run an agent

Ask an installed agent for one focused task.

/06

Review and test

Inspect changes and run the proper test command.

/07

Stop live processes

Stop sessions you no longer need.

/08

Update when ready

Use PAUITerm → Check for Updates.

Ready state

You are finished when the project opens from the rail, its terminal starts in the correct folder, optional agents launch without PATH or login errors, saved commands run from the intended working directory, and edited files remain in the original local folder.

12
Recovery

Fix the most common setup problems

Start with the exact executable, folder, shell, and account involved. Most first-run failures are a missing PATH entry or incomplete CLI authentication.

Agent says executable was not found in PATH+

Run the CLI version command in your system terminal, fully restart PAUITerm, and retry. If needed, use the full executable path returned by which codex or which claude on macOS, or Get-Command codex on PowerShell.

The agent asks for login or immediately exits+

Run the CLI directly outside PAUITerm and finish its browser, device-code, API-key, or provider login. Confirm a normal prompt works before restarting the PAUITerm agent.

The Ollama agent cannot start or find its model+

Open the Ollama application or start the Ollama service, run ollama --version, and test ollama run llama3 in your system terminal. If you selected another model, use its exact downloaded name in the PAUITerm Arguments field.

npm is missing+

Install a current Node.js LTS release, then reopen the terminal. npm normally arrives with Node.js. Do not use sudo for global AI CLI installation; use a Node version manager or user-writable global prefix if permissions fail.

A command exits immediately+

This is normal for one-time commands when they finish. Check the pane output for an error. Disable auto-restart for tests, builds, migrations, and other finite tasks.

A seventh pane will not open+

Each project displays up to six workspace panes. Close one, then open the new session. Closing a pane and stopping a live session are separate actions.

Port already in use+

Stop the older terminal or command that owns the port. If it started outside PAUITerm, stop that external process before restarting the dev server.

No inline terminal suggestion appears+

Inline ghost suggestions depend on PAUITerm shell integration for zsh, bash, or fish. PowerShell, cmd, WSL, Nushell, and other shells still work normally without this feature.

Local VS Code Web is unavailable+

Switch to PAUITerm Editor, or install and expose OpenVSCode Server, code-server, or a compatible VS Code CLI in PATH. PAUITerm does not download that server at runtime.

Keep this guide nearby

Return after installing a new CLI, changing shells, or moving a project folder.