♻️ Move agent configs under agents

Makefile

···
 code:
 	@ $(DOTFILES)/code/setup.sh
 
-.PHONY: claude
-claude:
-	@ command -v claude >/dev/null 2>&1 || curl -fsSL http://claude.ai/install.sh | bash
-	@ mkdir -p "$(HOME)/.claude"
-	@ ln -sf $(DOTFILES)/claude/settings.json "$(HOME)/.claude/settings.json"
-	@ ln -sf $(DOTFILES)/claude/CLAUDE.md "$(HOME)/.claude/CLAUDE.md"
-	@ ln -sfT $(DOTFILES)/claude/commands "$(HOME)/.claude/commands"
-	@ ln -sfT $(DOTFILES)/claude/agents "$(HOME)/.claude/agents"
-
-.PHONY: codex
-codex:
-	@ $(DOTFILES)/codex/setup.sh
+.PHONY: agents
+agents:
+	@ $(DOTFILES)/agents/setup.sh
 
 .PHONY: cursor
 cursor:

README.md

···
 - **Terminal**: [Alacritty](https://github.com/alacritty/alacritty)
 - **Theme**: [Catppuccin](https://github.com/catppuccin/catppuccin) (Frappe flavor)
 - **Shell**: `zsh` with [Starship](https://starship.rs/) prompt and [Sheldon](https://sheldon.cli.rs/) plugin manager
-- **Coding**: VS Code and Claude Code
+- **Coding**: VS Code, Codex, and Pi
 - **Note-taking**: VS Code with Foam Extension
 
 ## 📦 Configuration

agents/setup.sh

···
+#!/usr/bin/env bash
+set -euo pipefail
+
+DOTFILES="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+AGENTS_DIR="${DOTFILES}/agents"
+CODEX_DIR="${HOME}/.codex"
+
+setup_codex() {
+  paru -S --needed --noconfirm openai-codex-autoup-bin
+
+  mkdir -p "${CODEX_DIR}"
+  ln -sf "${AGENTS_DIR}/codex/config.toml" "${CODEX_DIR}/config.toml"
+  ln -sf "${AGENTS_DIR}/AGENTS.md" "${CODEX_DIR}/AGENTS.md"
+  ln -sfT "${AGENTS_DIR}/prompts" "${CODEX_DIR}/prompts"
+  ln -sfT "${AGENTS_DIR}/skills" "${CODEX_DIR}/skills"
+}
+
+setup_pi() {
+  npm install -g @mariozechner/pi-coding-agent
+}
+
+usage() {
+  echo "Usage: $(basename "$0") [codex|pi|all]" >&2
+  exit 1
+}
+
+if [[ $# -gt 1 ]]; then
+  usage
+fi
+
+if [[ $# -eq 0 ]] || [[ $1 == "all" ]]; then
+  setup_codex
+  setup_pi
+  exit 0
+fi
+
+if [[ $1 == "codex" ]]; then
+  setup_codex
+  exit 0
+fi
+
+if [[ $1 == "pi" ]]; then
+  setup_pi
+  exit 0
+fi
+
+usage

claude/CLAUDE.md

···
-../codex/AGENTS.md

claude/commands/commit.md

···
----
-allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git diff:*), Bash(git log:*)
-description: Create well-formatted commits with the conventional commits style mixed with emoji (gitmoji).
----
-
-# Commit
-
-## Context
-
-- Current git status: !`git status`
-- Current git diff (staged and unstaged changes): !`git diff HEAD`
-- Current branch: !`git branch --show-current`
-- Recent commits: !`git log --oneline -40`
-
-## Goal
-
-Create well-formatted commits with the conventional commits style mixed with emoji (gitmoji).
-
-1. Checks which files are staged with `git status`.
-2. Check historical commits to learn style and tone (`git log --oneline -40`).
-3. Analyze the diff to determine if multiple distinct logical changes are present.
-4. If multiple distinct changes are detected, break the commit into multiple smaller commits.
-5. For each commit (or the single commit if not split), create a commit message using the commit convention.
-   1. Add all relevant changes with `git add`.
-   2. Performs a `git diff` to understand what actual changes are being committed
-   3. Write the descriptive and concise commit message.
-
-## Commit Style
-
-- **Atomic commits**: Each commit should contain related changes that serve a single purpose.
-- **Split large changes**: If changes touch multiple concerns, split them into separate commits. Always reviews the commit diff to ensure the message matches the changes
-- **Concise first line**: Keep the first line under 72 characters. Do not end the subject line with a period.
-- **Present tense, imperative mood**: Use the imperative mood in the subject line.
-- **Conventional commit format**: Use the format `<emoji> <description>`.
-
-### Emoji Inspiration
-
-  - 🎨 Improve structure / format of the code
-  - ⚡️ Improve performance
-  - 🔥 Remove code or files
-  - 🐛 Fix a bug
-  - 🚑️ Critical hotfix
-  - ✨ Introduce new features
-  - 📝 Add or update documentation
-  - 🚀 Deploy stuff
-  - 💄 Add or update the UI and style files
-  - 🎉 Begin a project
-  - ✅ Add, update, or pass tests
-  - 🔒️ Fix security or privacy issues
-  - 🔐 Add or update secrets
-  - 🔖 Release / Version tags
-  - 🚨 Fix compiler / linter warnings
-  - 🚧 Work in progress
-  - 💚 Fix CI Build
-  - ⬇️ Downgrade dependencies
-  - ⬆️ Upgrade dependencies
-  - 📌 Pin dependencies to specific versions
-  - 👷 Add or update CI build system
-  - 📈 Add or update analytics or track code
-  - ♻️ Refactor code
-  - ➕ Add a dependency
-  - ➖ Remove a dependency
-  - 🔧 Add or update configuration files
-  - 🔨 Add or update development scripts
-  - 🌐 Internationalization and localization
-  - ✏️ Fix typos
-  - 💩 Write bad code that needs to be improved
-  - ⏪️ Revert changes
-  - 🔀 Merge branches
-  - 📦️ Add or update compiled files or packages
-  - 👽️ Update code due to external API changes
-  - 🚚 Move or rename resources (e.g.: files, paths, routes)
-  - 📄 Add or update license
-  - 💥 Introduce breaking changes
-  - 🍱 Add or update assets
-  - ♿️ Improve accessibility
-  - 💡 Add or update comments in source code
-  - 🍻 Write code drunkenly
-  - 💬 Add or update text and literals
-  - 🗃️ Perform database related changes
-  - 🔊 Add or update logs
-  - 🔇 Remove logs
-  - 👥 Add or update contributor(s)
-  - 🚸 Improve user experience / usability
-  - 🏗️ Make architectural changes
-  - 📱 Work on responsive design
-  - 🤡 Mock things
-  - 🥚 Add or update an easter egg
-  - 🙈 Add or update a .gitignore file
-  - 📸 Add or update snapshots
-  - ⚗️ Perform experiments
-  - 🔍️ Improve SEO
-  - 🏷️ Add or update types
-  - 🌱 Add or update seed files
-  - 🚩 Add, update, or remove feature flags
-  - 🥅 Catch errors
-  - 💫 Add or update animations and transitions
-  - 🗑️ Deprecate code that needs to be cleaned up
-  - 🛂 Work on code related to authorization, roles and permissions
-  - 🩹 Simple fix for a non-critical issue
-  - 🧐 Data exploration/inspection
-  - ⚰️ Remove dead code
-  - 🧪 Add a failing test
-  - 👔 Add or update business logic
-  - 🩺 Add or update healthcheck
-  - 🧱 Infrastructure related changes
-  - 🧑‍💻 Improve developer experience
-  - 💸 Add sponsorships or money related infrastructure
-  - 🧵 Add or update code related to multithreading or concurrency
-  - 🦺 Add or update code related to validation
-  - ✈️ Improve offline support
-
-## Guidelines for Splitting Commits
-
-When analyzing the diff, consider splitting commits based on these criteria:
-
-1. **Different concerns**: Changes to unrelated parts of the codebase
-2. **Different types of changes**: Mixing features, fixes, refactoring, etc.
-3. **File patterns**: Changes to different types of files (e.g., source code vs documentation)
-4. **Logical grouping**: Changes that would be easier to understand or review separately
-5. **Size**: Very large changes that would be clearer if broken down
-
-## Examples
-
-- ✨ Add user authentication system
-- 🐛 Resolve memory leak in rendering process
-- 📝 Update API documentation with new endpoints
-- ♻️ Simplify error handling logic in parser
-- 🚨 Resolve linter warnings in component files
-- 🧑‍💻 Improve developer tooling setup process
-- 👔 Implement business logic for transaction validation
-- 🩹 Address minor styling inconsistency in header
-- 🚑️ Patch critical security vulnerability in auth flow
-- 🎨 Reorganize component structure for better readability
-- 🔥 Remove deprecated legacy code
-- 🦺 Add input validation for user registration form
-- 💚 Resolve failing CI pipeline tests
-- 📈 Implement analytics tracking for user engagement
-- 🔒️ Strengthen authentication password requirements
-- ♿️ Improve form accessibility for screen readers

claude/commands/plan.md

···
-# Plan
-
-Create clear, actionable, and efficient plans.
-
-1. **Clarify First**
-   - Ask targeted questions to understand the goal, constraints, and success criteria
-   - Identify any ambiguities or assumptions that need validation
-   - Confirm the scope and boundaries of the task
-
-2. **Optimize for Simplicity**
-   - Start with the minimal viable solution
-   - Check if the goal can be achieved by modifying existing solutions
-   - Consider if anything can be removed rather than added
-   - Prefer straightforward approaches over complex ones
-
-3. **Break Down into Atomic Steps**
-   - Decompose the task into small, independent, testable units
-   - Each step should have a clear input, action, and output
-   - Steps should be executable in isolation when possible
-   - Include verification/testing criteria for each step
-
-4. **Structure Your Plan**
-   - Prerequisites: What needs to be in place before starting
-   - Steps: Numbered, actionable tasks with clear outcomes
-   - Dependencies: Which steps rely on others
-   - Checkpoints: Where to verify progress and adjust if needed
-   - Success Criteria: How to know when the plan is complete
-
-5. **Consider Edge Cases**
-   - What could go wrong at each step?
-   - What are the fallback options?
-   - Where might iterations be needed?
-
-## Output Format
-
-Present your plan as:
-1. Goal Statement (one clear sentence)
-2. Clarifying Questions (if any)
-3. Prerequisites
-4. Step-by-Step Plan (numbered, with sub-steps as needed)
-5. Success Metrics
-6. Potential Risks & Mitigations

claude/commands/question.md

···
-# Question
-
-Answer user questions directly and accurately. Focus on providing information. Use all the tools you need but don't make any changes (code or system).
-
-## Process
-
-1. **Parse the question**: Identify the core question and any sub-questions
-2. **Gather context**: Use search tools to find relevant resources (online and local). Ask clarifying questions if the question is ambiguous or need more details
-3. **Analyze systematically**: Consider multiple perspectives, edge cases, and potential blind spots
-4. **Respond with specifics**: Give concrete answers and actionable next steps. Discuss trade-offs, which you prefer, ...
-
-## Response Format
-
-- Start with a direct answer (1-2 sentences)
-- Provide supporting details with specific references (`file:line`)
-- End with concrete next steps if applicable
-- Keep total response under 10 lines unless complexity requires more
-
-## Constraints
-
-- No file modifications or system changes
-- Prioritize accuracy over speed
-- Push back on unclear or impossible requests

claude/commands/simplify.md

···
-# Simplify
-
-Refactor code (#$ARGUMENTS) to be simpler while maintaining identical functionality. Simple code is easier to understand, change, debug and more flexible, not just shorter.
-
-## Steps
-
-1. **Analyze** - Understand purpose, identify edge cases
-2. **Remove** - Dead code, unused variables, redundant operations
-3. **Simplify** - Complex conditionals, verbose constructs, unnecessary state
-4. **Restructure** - Extract common code, flatten nesting, use early returns
-5. **Verify** - Test that behavior remains identical
-
-## Focus Areas
-
-- Replace custom implementations with built-ins
-- Combine similar functions
-- Use clearest variable/function names
-- Apply KISS principle
-
-## Constraints
-
-- MUST produce identical outputs for all inputs
-- MUST maintain same public API/interface

claude/settings.json

···
-{
-  "includeCoAuthoredBy": false,
-  "permissions": {
-    "allow": [
-      "Bash(git:*)",
-      "Bash(python:*)",
-      "Bash(uv run:*)",
-      "Bash(ls:*)",
-      "Bash(make:*)",
-      "Bash(mkdir:*)",
-      "Bash(cat:*)",
-      "Bash(cp:*)",
-      "Bash(find:*)",
-      "Bash(rg:*)",
-      "Bash(grep:*)",
-      "Bash(time:*)",
-      "Bash(gh:*)",
-      "Edit(**)",
-      "WebFetch(domain:github.com)",
-      "WebFetch(domain:raw.githubusercontent.com)",
-      "WebFetch(domain:*)"
-    ],
-    "deny": []
-  },
-  "alwaysThinkingEnabled": true
-}

codex/agents/.gitignore

···
-auth.json
-**/sessions/

codex/agents/cdx-weaver/AGENTS.md

···
-You are an expert note-linker and synthesizer. Your job is to enrich the given text with relevant ideas, insights, learnings and key points from a collection of markdown notes. You connect ideas across notes and integrate them seamlessly into writing.
-
-## Instructions
-
-1. Read the text carefully understanding the different areas and topics it touchees.
-2. List all Handbook notes using `find ~/projects/handbook/ -name "*.md" -exec basename {} \;`.
-3. Read all relevant notes that might contain useful information given the text.
-4. Search for relevant keywords across the notes to discover other potentially interesting notes.
-5. Integrate the information into the text while preserving tone, structure, and intent.
-6. Output the revised text in a code block.
-7. Output an idea list with learnings and key points from the notes that might apply to the text but were not included.
-
-Don't make any edits to handbook notes or other files. Avoid fluff and unnecessary changes.
-
-### Examples
-
-- If the text describes a system, consult the `Systems.md` note and ensure key design principles are included or surfaced in the list.
-- If the text is about solving a problem, consult the Problem Solving note and check it follows those practices.
-
-## Goal
-
-Augment the provided text with any valuable ideas, principles, insights, and learnings found in the Handbook notes.

codex/agents/cdx-weaver/config.toml

···
-model = "gpt-5.1"
-model_reasoning_effort = "high"
-approval_policy = "never"
-sandbox_mode = "read-only"
-project_doc_max_bytes = 0
-project_doc_fallback_filenames = []
-
-[features]
-unified_exec = true
-streamable_shell = true
-web_search_request = true

codex/setup.sh

···
-#!/usr/bin/env bash
-set -euo pipefail
-
-DOTFILES=$(dirname "$(dirname "$(realpath "$0")")")
-CODEX_DIR="${HOME}/.codex"
-
-paru -S --needed --noconfirm openai-codex-autoup-bin
-
-mkdir -p "${CODEX_DIR}"
-
-ln -sf "${DOTFILES}/codex/config.toml" "${CODEX_DIR}/config.toml"
-ln -sf "${DOTFILES}/codex/AGENTS.md" "${CODEX_DIR}/AGENTS.md"
-ln -sfT "${DOTFILES}/codex/prompts" "${CODEX_DIR}/prompts"
-ln -sfT "${DOTFILES}/codex/skills" "${CODEX_DIR}/skills"

scripts/cdx-weaver

···
-#!/usr/bin/env bash
-
-set -euo pipefail
-
-REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-AGENT_DIR="${REPO_ROOT}/codex/agents/cdx-weaver"
-
-if [[ ! -d $AGENT_DIR ]]; then
-  echo "Error: agent directory not found at $AGENT_DIR" >&2
-  exit 1
-fi
-
-usage() {
-  echo "Usage: $(basename "$0") [file|-]  (reads stdin when no file is provided or when using '-')" >&2
-  exit 1
-}
-
-if (( $# > 1 )); then
-  usage
-fi
-
-if (( $# == 1 )) && [[ $1 != "-" ]]; then
-  if [[ ! -f $1 ]]; then
-    echo "Error: file not found: $1" >&2
-    exit 1
-  fi
-  CONTENT=$(cat "$1")
-else
-  if [ -t 0 ]; then
-    usage
-  fi
-  CONTENT=$(cat)
-fi
-
-if [[ -z "${CONTENT//[[:space:]]/}" ]]; then
-  echo "Error: no input provided" >&2
-  exit 1
-fi
-
-# Wrap the content in XML tags
-PROMPT=$(cat <<EOF
-Enhance any given text by enriching it with relevant insights drawn from the Handbook notes.
-
-<text>
-${CONTENT}
-</text>
-EOF
-)
-
-# Run Codex in exec mode
-env CODEX_HOME="$AGENT_DIR" \
-  codex exec \
-    --skip-git-repo-check \
-    --color=never \
-    "$PROMPT"

terminal/zshrc

···
 
 # Functions
 aigcm() {
-  tmux new-session -d -s "aigcm-$(date +%s)" "codex exec - < $HOME/projects/dotfiles/codex/prompts/commit.md"
+  tmux new-session -d -s "aigcm-$(date +%s)" "codex exec - < $HOME/projects/dotfiles/agents/prompts/commit.md"
 }
 
 qgs() {