overthinkos/charly-cachyos

charly-cachyos

The operator's CachyOS developer-workstation profile: a kind: local template (local.charly-cachyos) plus a target: local + host: local deploy entry (deploy.charly-cachyos) that applies a kitchen-sink dev stack directly to the current machine via ShellExecutor — no SSH, no VM, no container.

It lives in the overthinkos/cachyos repo (git submodule at box/cachyos), in that repo's config (its charly.yml + per-kind sibling files) — both the kind: local template and its kind: deploy entry (deploy.charly-cachyos). The repo also carries a sibling kind: deploy, deploy.cachyos-gpu — the persistent operator GPU-workstation VM (target: vm, not disposable; see /charly-vm:cachyos) — so charly-cachyos is no longer the only kind: deploy there; every disposable test bed remains kind: eval. Apply it with:

charly -C box/cachyos update charly-cachyos
# or, anywhere:
charly --repo overthinkos/cachyos update charly-cachyos

What it installs

30 candies. Most are pulled from the main repo by git reference (@github.com/overthinkos/overthink/candy/<name>:<tag>); the cachyos-exclusive ghostty, keepassxc-keyring, and wheel-nopasswd are vendored locally in this repo's candy/ (resolved via its discover: block):

wheel-nopasswd, yay, dev-tools, gh, pre-commit, tmux, direnv, gnupg, keepassxc, keepassxc-keyring, tailscale, tailscale-up, build-toolchain, golang, rust, nodejs, uv, claude-code, codex, gemini, oracle, forgecode, devops-tools, docker-ce, kubernetes, vscode, ghostty, chrome, nvidia, charly.

Key fields

| Field | Value | |---|---| | install_opts.builder_image | ghcr.io/overthinkos/arch-builder:2026.122.2252 (OCI ref, not a candy) | | install_opts | with_service, allow_repo_changes, allow_root_tasks all true | | env | EDITOR=nvim, PAGER=less | | disposable (deploy) | true — charly update charly-cachyos is authorized |

Deploy-scope eval probes

• passwordless-sudo-host — sudo -n true (wheel-nopasswd candy must have run)
• nvidia-ctk-present — command -v nvidia-ctk
• nvidia-cdi-spec — /etc/cdi/nvidia.yaml exists

Both nvidia-* probes gate on an active host NVIDIA driver ([ -e /dev/nvidiactl ] || nvidia-smi) and pass with an N/A note on a card-less or VFIO-passthrough host, so the profile applies cleanly anywhere.

Composition-by-reference note

local.charly-cachyos's remote candy refs are collected and materialized by the same CollectRemoteRefs walk as box candy refs: the walk collects the candy refs of the ROOT project's own kind: local templates (charly-cachyos is the root here), so charly box validate / charly update charly-cachyos resolve the github-ref'd candies. (Collection is reachability-scoped — a namespace's kind:local templates, imported only as a dependency, are NOT collected by an importer; only the root's own locals are. See /charly-internals:go "Remote-layer resolver".)

Cross-References

• /charly-local:local-spec — kind: local template authoring reference
• /charly-local:local-deploy — the target: local deployment surface
• /charly-distros:cachyos — the CachyOS base of the same family
• /charly-core:deploy — deploy entry semantics (cross-kind name reuse: deploy.charly-cachyos ↔ local.charly-cachyos)

When to Use This Skill

MUST be invoked when editing or applying the charly-cachyos workstation profile, or reasoning about the kind:local remote-candy-ref machinery. Invoke BEFORE reading source code or launching Explore agents.