aic documentation
aic is a local-first AI coding configuration manager with a unified TUI as its primary entry point. It manages Skills, Context, MCP servers, environment variables, permissions, and providers for Claude, Codex, Gemini, and OpenCode — all from one TUI that fits naturally into your terminal workflow.
One-liner
One TUI for Skills, Context, MCP, Env, Permission, and Provider across Claude, Codex, Gemini, and OpenCode.
What’s in this documentation
- Quick start: run
aicto see the TUI first, then reach for CLI when you need scripting. - Core concepts: TUI, Skills, Context, MCP, Env, Permission, Provider, Registry, Link mode.
- Shortcuts and commands: TUI key bindings by panel and a CLI cheat sheet.
- Configuration and paths: project
.aic/, user~/.aic/, and tool link paths. - Provider configuration: Provider multi-model config file paths, naming conventions, and switching methods for Claude / Codex / Gemini / OpenCode.
- AI tool installation: official install commands and config paths for Claude Code / Codex / Gemini / OpenCode.
- Trust and local-first boundaries: which local files aic reads and writes, what to commit and what to keep out of Git.
- Troubleshooting: common issues across install, sync, Registry, Env, Provider, and TUI.
- Why aic: why TUI first instead of CLI.
- Glossary: centralized definitions for terms used across the docs.
- Contact: author email and Registry repository.
Design orientation
- TUI is the primary entry point; CLI is auxiliary (scripting, remote environments, CI integration).
- Local-first: project config lives in
<project>/.aic/, user config in~/.aic/, sensitive env values never reach a database. - Portable: team conventions travel with the project — clone and
aic syncto restore the full setup. - Restrained: no accounts, no cloud sync, no billing, no paywalls.
Languages
Chinese is the source language (sourceLocale: zh). The English version is a natural translation with technical terms preserved in their original form. If the two diverge, the Chinese version prevails.