me

me gives a Mac pirog's tools, dotfiles, habits, and prejudices—and gives Codex a job beyond producing agreeable paragraphs. workstation setup and GitHub-backed task work, in one editable profile.

use it as:

• an operator profile to set up a computer for manual use as pirog.
• a Codex binding to have Codex work with pirog's guidance and preferences, automate assigned GitHub issue work, and review pull requests on request.

we recommend using both.

requires macOS 26 or newer. see Inventory for what ships and Piroboot for bootstrap options.

for workstation and Codex setup, provide a 1Password service account token and run the hosted bootstrap. it installs applications and dotfiles and retrieves the configured private SSH keys:

/bin/bash -c "$(curl -fsSL https://boot.pirog.me/boot.sh)" piroboot \
  --op-token "$OP_TOKEN" \
  --tanaab canon:codex-plugin \
  --tanaab openclaw-agent-system:codex-plugin-build

for workstation-only setup, omit the two --tanaab selections. see Piroboot for the full option reference.

for the skills alone, install piroplugin without running the machine bootstrap:

npx --yes --package=@tanaab/codex-tools@1 -- codex-tools install npm:@pirog/me@latest --marketplace pirostore

piro-skill-author also requires the Canon (tanaab) plugin for shared authoring and validation.

pirog's me profile ships with:

• Piroboot: the workstation bootstrap script.
• dependencies: applications and command-line tools.
• dotfiles: Stow-managed user configuration.
• plugins: the Pirostore catalog and local source links.
• skills: assessment, implementation, replies, authoring, and voice.
• automations: issue assignments, updates, and validation jobs.
• configuration files: the sources that define the profile.
• a cheat sheet: common commands and Codex prompts.

• 1Password: sign in, unlock, and enable Developer > Integrate with 1Password CLI and Show 1Password Developer experience. keep the beta CLI for 1Password Environments; check access with op vault list.
• Tailscale: if using the desktop app, sign in and join tanaab.dev. leave formula-backed services in place; tailscale status --json should report the local node running and online.

the quickstart's two --tanaab options install Agent System (agent-system) and Canon (tanaab). sign into Codex, install piroplugin from Pirostore, and confirm all three plugins are enabled.

connect GitHub as pirog for ordinary pirog work. authorize Agent System's hook and Piroplugin's account-policy hooks through /hooks, start a fresh chat, and paste:

Use $agent-system-codex-binding to bind this plugin to /Users/pirog/tanaab/me.

confirm the workspace containing .agent-system/agent.yaml. binding sets up private account defaults for pirog and tanaabot. missing defaults trigger setup when needed; ask Codex Binding to “update my account defaults” to change them.

after binding, start a fresh chat and paste:

Use $agent-system-doctor to check this workspace. Then use $agent-system-install
for any declared setup repairs and to reconcile its automations.
Run $agent-system-doctor again and report anything still unresolved.

paste the prompt you need into Codex, replacing the placeholder:

# start or resume an issue without assigning it or enabling scheduled intake
use $agent-system-task-launch to work on <issue URL>.

# continue an existing same-repository PR
use $agent-system-task-launch to continue <PR URL>.

# retire managed work without closing the GitHub issue
use $agent-system-task-retirement to clean up <issue URL>.

# clean up one explicitly selected unmanaged chat
use $agent-system-task-retirement to clean up chat <exact chat ID>.

# check workspace readiness without applying repairs
use $agent-system-doctor to check this workspace.

# rewrite supplied prose in the shared voice
use $piro-voice to rewrite the following text: <text>.

see the full cheat sheet for maintenance and other prompts.

for automatic pickup, set up assignment intake once, then assign work through GitHub:

1. configure approved assigners, repository owners, and the workflow mode in the profile. see Agent System's GitHub workflow configuration.
2. use $agent-system-install to activate and reconcile intake, then $agent-system-doctor to check saved state. see the Codex automation contract for how scheduled jobs are managed.
3. have an approved assigner assign an eligible issue to @pirog. include a clear outcome, acceptance criteria, and a reproduction for bugs. follow progress in its Codex chat and review any resulting PR.

Doctor checks saved state; a successful scheduled run is separate evidence.

use the runtimes in .node-version and .bun-version:

# prepare the checkout
git clone git@github.com:pirog/me.git
cd me
bun install --frozen-lockfile --ignore-scripts

# run tests, lint, formatting, and ShellCheck
bun run test
bun run lint

edit the source configuration, not generated files. bun run build and Leia scenarios are CI-owned by default: they generate dist/ or mutate macOS runner state. read the example guidance before changing executable examples.

bring bugs, regressions, and feature requests to the GitHub issue queue. see CHANGELOG.md and GitHub releases for changes. piroplugin releases ship through npm; see plugin sources.

• @pirog

made with contrib.rocks.