The canonical repo is git.zacharyzhang.com now, so every URL a user can actually reach had to move with it. Self-updater: `PRODUCTION_ENDPOINTS.update_base_url` targets Gitea's `/api/v1/repos/.../releases`, which serves the same wire format GitHub's releases API did — `Release`/asset deserialisation is unchanged. The alpha channel requests `?per_page=30&limit=30` because GitHub reads the page size from `per_page` and Gitea from `limit`, and each ignores the other's, so one URL stays correct on either. Installers: same API base, and the documented one-liners become `https://kigicli.dev/install.{sh,ps1}`. That domain's Worker proxies both files from Gitea raw `main`, so the published install command survives any future forge move without being reprinted everywhere. install.ps1 also drops the GitHub-specific `Accept: application/vnd.github+json`. Everything else user-facing: `/feedback` and the shell's feedback fallback point at the Gitea issue tracker, `/docs` at the Gitea-rendered README, and web_fetch's User-Agent at kigicli.dev. SECURITY.md now routes reports to the issue tracker with a warning to withhold exploitable detail, because Gitea has no equivalent of GitHub's private vulnerability reporting. Comments naming `.github/workflows/release.yml` name `.gitea/` now. Tests assert against these constants rather than literal URLs, so they follow automatically; the one URL-shape assertion (production endpoints are https) still holds. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
kigi-tui
Terminal UI (TUI) for Kigi. Provides the interactive full-screen interface including the scrollback view, prompt input, session management, and all modal dialogs.
Architecture
src/
├── app/ # Application state and event handling
│ ├── app_view.rs # Top-level state (welcome screen, agents, config)
│ ├── agent_view/ # Per-session agent view (struct in mod.rs + per-domain impl modules)
│ ├── dispatch/ # Action → Effect dispatcher (router + per-domain modules)
│ ├── effects.rs # Async side effects (ACP calls, file I/O)
│ └── event_loop.rs # Main event loop (input, ticks, ACP messages)
├── views/ # UI components
│ ├── prompt_widget.rs # Text editor with file search, slash, history
│ ├── welcome/ # Welcome screen (logo, menu, prompt)
│ ├── extensions_modal.rs # Extensions modal (hooks, plugins, marketplace, skills, MCP servers)
│ ├── file_search/ # @-completion dropdown and line viewer
│ ├── slash_dropdown.rs# /command completion dropdown
│ └── ... # Scrollback, status bar, panes, etc.
├── scrollback/ # Message history rendering
├── slash/ # Slash command registry and built-in commands
├── appearance/ # Theme and pager.toml config
├── acp/ # Agent Communication Protocol client state
└── render/ # Low-level rendering helpers (color, wrapping, etc.)
Key Concepts
- AppView — owns the welcome screen, agent sessions, and global config
- AgentView — one per session; owns the prompt, scrollback, tool panes, and modals
- PromptWidget — text editor component with file search (
@), slash commands (/), history search, and paste elements - Action/Effect — Elm-style architecture: input → Action → dispatch → Effect → state update
Keyboard Shortcuts
| Key | Context | Action |
|---|---|---|
Ctrl+P or ? |
Agent screen | Open command palette |
Ctrl+L |
Any (non–VS Code family) | Open plugins/hooks modal; on VS Code / Cursor / Windsurf / Zed use /plugins or /hooks (Ctrl+L is mid-turn interject) |
Tab |
Prompt | Switch to scrollback |
Esc |
Turn running | No-op (does not cancel; use Ctrl+C) |
Esc Esc |
Idle, non-empty prompt | Clear prompt (within 800ms; first press shows hint) |
Esc Esc |
Idle, empty prompt + messages | Open rewind picker (silent first press) |
Ctrl+M |
Prompt | Toggle multiline mode |
Shift+Enter |
Prompt | Insert newline |
/ |
Prompt | Start slash command |
@ |
Prompt | Start file search |
! |
Prompt (empty) | Enter bash mode |
Ctrl+C |
Prompt (with text) | Clear prompt (even while turn running) |
Ctrl+C |
Prompt (empty) + turn running | Cancel running turn |
Docs
- Terminal Support & Troubleshooting — tmux/SSH truecolor, clipboard, mouse, diagnostics, /terminal-setup
- Hooks & Plugins Guide — managing hooks, plugins, and marketplace sources
- Custom Hooks Guide — creating, configuring, and writing your own hooks
- Hook Examples — sample hooks for common workflows
- Hooks Crate (
kigi-hooks) — hook runtime, event types, and execution engine - Plugin Marketplace Crate (
kigi-plugin-marketplace) — marketplace source loading, scanning, and install