Coding Agents Setup

A modern local toolchain setup for coding agents. It installs or writes user-level configuration for Codex and Claude, with Windows and Linux behavior kept separate.

TL;DR

This repo turns local coding-agent conventions into installable rule files and setup scripts: available tools, package-manager preferences, file deletion behavior, operations that require user confirmation, and platform differences.

It has a clear preference for newer tools: uv for Python, bun for JavaScript/TypeScript, and command-line replacements such as rg, fd, and eza.

Managed config files are backed up before replacement. CI runs installation and behavior smoke checks on Ubuntu and Windows, which gives a basic reliability check but cannot cover every local environment.

Install

Review the scripts before running remote bootstrap commands. They download code and execute it locally.

By default, bootstrap downloads the commit from the latest successful GitHub Actions smoke run triggered by a ci-* tag.

Windows:

irm https://raw.githubusercontent.com/NihilDigit/coding-agents-setup/main/install.ps1 | iex

Linux:

curl -fsSL https://raw.githubusercontent.com/NihilDigit/coding-agents-setup/main/install.sh | bash

From a cloned checkout:

.\setup-windows.ps1 -Agent Both

./setup-linux.sh --agent both

Test a branch instead of the latest tested tag:

curl -fsSL https://raw.githubusercontent.com/NihilDigit/coding-agents-setup/main/install.sh | REF=main REF_KIND=branch bash

& ([scriptblock]::Create((irm https://raw.githubusercontent.com/NihilDigit/coding-agents-setup/main/install.ps1))) -Ref main -RefKind branch

Windows

Windows is the full interactive setup. It can install the toolchain, write Codex/Claude rule files, write a PowerShell profile, make rm send files to the Recycle Bin, set up Agent Skills directories, install rtk, and optionally install Kimi WebBridge.

The Windows bootstrap installs PowerShell 7 (pwsh) by default, runs setup through it, sets the current user's execution policy to RemoteSigned, and tries to make PowerShell 7 the default Windows Terminal profile. If a cloned checkout is blocked before the script can start, launch it once with:

powershell -ExecutionPolicy Bypass -File .\setup-windows.ps1 -Agent Both

PowerShell profile writing is interactive. The default profile adds PATH entries and helper functions. A second prompt enables Unix-style aliases, including safe rm -> trash shadowing; the default is yes.

Kimi WebBridge is offered by default and can be declined. It downloads and executes Kimi's current installer, and browser extension/profile access may be required for browser automation.

-Yes accepts every setup prompt, including prompts whose interactive default is no:

.\setup-windows.ps1 -Agent Both -Yes

Rules only:

.\setup-windows.ps1 -Agent Codex -SkipTools -SkipProfile

Linux

Linux distributions and desktop environments vary too much for one fixed install flow. The Linux setup writes rule files first, installs ~/.local/bin/clip-run, and includes a temporary first-run task for the agent to inspect the machine and ask what to configure.

It does not install system packages or modify shell profiles.

On Arch-like systems, generated rules add Arch-specific guidance: use paru -S or sudo pacman -S, prefer *-bin AUR packages when available, use system trash-cli, and configure sudoers narrowly for /usr/bin/pacman and /usr/bin/paru.

clip-run is used when an agent needs user confirmation or sudo: it writes a script to /tmp and copies the command for the user to run manually.

After the first Linux setup pass, delete the temporary Linux Initial Setup Task section from the generated agent file.

Safety

Silent install and update are acceptable when scoped to the requested setup. Silent deletion is not.

Persistent files are backed up before replacement:

• Linux: adjacent *.bak-<timestamp> backups for generated agent rules and ~/.local/bin/clip-run.
• Windows: backups under ~/.coding-agents-backup-<timestamp> for generated rules, PowerShell profiles, setup selection state, and ~/.local/bin/rtk.exe.
• Windows skills layout: existing ~/.claude/skills links or directories are moved to .old-<timestamp>.

Verify

Linux:

./verify-linux.sh --feature trash
./verify-linux.sh --command paru --feature arch-sudoers
./verify-linux.sh
bash tests/Smoke-Linux.sh

Windows:

.\verify-windows.ps1
.\tests\Smoke-Windows.ps1

Repository checks:

pwsh -NoLogo -NoProfile -File tests/Test-Setup.ps1

GitHub Actions runs smoke tests on Ubuntu and Windows when a ci-* tag is pushed:

tag="ci-$(date -u +%Y%m%d%H%M%S)"
git tag --no-sign "$tag"
git push origin "$tag"

Rule Fragments

Shared:

rules/AGENTS.shared.md
rules/AGENTS.codex.md
rules/CLAUDE.md

Platform:

rules/AGENTS.windows.md
rules/AGENTS.linux.md
rules/AGENTS.linux-arch.md
rules/AGENTS.linux-initial-setup.md

AGENTS.linux-arch.md is included only when /etc/os-release reports ID=arch or ID_LIKE contains arch.

Agent Targets

Windows -Agent: Codex, Claude, Both, None, Prompt.

Linux --agent: codex, claude, both, none, prompt.