chore: rebrand companion-os to clanker-agent

- Rename all package names from companion-* to clanker-*
- Update npm scopes from @mariozechner to @harivansh-afk
- Rename config directories .companion -> .clanker
- Rename environment variables COMPANION_* -> CLANKER_*
- Update all documentation, README files, and install scripts
- Rename package directories (companion-channels, companion-grind, companion-teams)
- Update GitHub URLs to harivansh-afk/clanker-agent
- Preserve full git history from companion-cloud monorepo
This commit is contained in:
Harivansh Rathi 2026-03-26 16:22:52 -04:00
parent f93fe7d1a0
commit 67168d8289
356 changed files with 2249 additions and 10223 deletions

View file

@ -1,4 +1,4 @@
> companion can create themes. Ask it to build one for your setup.
> clanker can create themes. Ask it to build one for your setup.
# Themes
@ -16,12 +16,12 @@ Themes are JSON files that define colors for the TUI.
## Locations
Companion loads themes from:
Clanker loads themes from:
- Built-in: `dark`, `light`
- Global: `~/.companion/agent/themes/*.json`
- Project: `.companion/themes/*.json`
- Packages: `themes/` directories or `companion.themes` entries in `package.json`
- Global: `~/.clanker/agent/themes/*.json`
- Project: `.clanker/themes/*.json`
- Packages: `themes/` directories or `clanker.themes` entries in `package.json`
- Settings: `themes` array with files or directories
- CLI: `--theme <path>` (repeatable)
@ -37,22 +37,22 @@ Select a theme via `/settings` or in `settings.json`:
}
```
On first run, companion detects your terminal background and defaults to `dark` or `light`.
On first run, clanker detects your terminal background and defaults to `dark` or `light`.
## Creating a Custom Theme
1. Create a theme file:
```bash
mkdir -p ~/.companion/agent/themes
vim ~/.companion/agent/themes/my-theme.json
mkdir -p ~/.clanker/agent/themes
vim ~/.clanker/agent/themes/my-theme.json
```
2. Define the theme with all required colors (see [Color Tokens](#color-tokens)):
```json
{
"$schema": "https://raw.githubusercontent.com/badlogic/companion-mono/main/packages/coding-agent/src/modes/interactive/theme/theme-schema.json",
"$schema": "https://raw.githubusercontent.com/badlogic/clanker-agent/main/packages/coding-agent/src/modes/interactive/theme/theme-schema.json",
"name": "my-theme",
"vars": {
"primary": "#00aaff",
@ -116,13 +116,13 @@ vim ~/.companion/agent/themes/my-theme.json
3. Select the theme via `/settings`.
**Hot reload:** When you edit the currently active custom theme file, companion reloads it automatically for immediate visual feedback.
**Hot reload:** When you edit the currently active custom theme file, clanker reloads it automatically for immediate visual feedback.
## Theme Format
```json
{
"$schema": "https://raw.githubusercontent.com/badlogic/companion-mono/main/packages/coding-agent/src/modes/interactive/theme/theme-schema.json",
"$schema": "https://raw.githubusercontent.com/badlogic/clanker-agent/main/packages/coding-agent/src/modes/interactive/theme/theme-schema.json",
"name": "my-theme",
"vars": {
"blue": "#0066cc",
@ -268,7 +268,7 @@ Four formats are supported:
### Terminal Compatibility
Companion uses 24-bit RGB colors. Most modern terminals support this (iTerm2, Kitty, WezTerm, Windows Terminal, VS Code). For older terminals with only 256-color support, companion falls back to the nearest approximation.
Clanker uses 24-bit RGB colors. Most modern terminals support this (iTerm2, Kitty, WezTerm, Windows Terminal, VS Code). For older terminals with only 256-color support, clanker falls back to the nearest approximation.
Check truecolor support: