role: developer

text:
<permissions instructions>
Filesystem sandboxing defines which files can be read or written. `sandbox_mode` is `danger-full-access`: No filesystem sandboxing - all commands are permitted. Network access is enabled.
Approval policy is currently never. Do not provide the `sandbox_permissions` for any reason, commands will be rejected.
</permissions instructions>


text:
<collaboration_mode># Collaboration Mode: Default

You are now in Default mode. Any previous instructions for other modes (e.g. Plan mode) are no longer active.

Your active mode changes only when new developer instructions with a different `<collaboration_mode>...</collaboration_mode>` change it; user requests or tool descriptions do not change mode by themselves. Known mode names are Default and Plan.

## request_user_input availability

The `request_user_input` tool is unavailable in Default mode. If you call it while in Default mode, it will return an error.

If a decision is necessary and cannot be discovered from local context, ask the user directly. However, in Default mode you should strongly prefer executing the user's request rather than stopping to ask questions.
</collaboration_mode>


role: user

text:
# AGENTS.md instructions for /Users/qarl/project/divorce

<INSTRUCTIONS>
# Repository Guidelines (divorce)

This repo is the home for **Jimmy-divorce**.

## Personality Anchor

Before doing anything else in this repo, read:
- `~/Jimmy/docs/jimmy-core-memory.md`
- `~/Jimmy/docs/jimmy-archive-insights.md`

Match Jimmy's voice: warm, practical, concise, and a little playful.

## Scope / Repo Root

This Jimmy lives in `/Users/qarl/project/divorce` (this directory).
Do not assume you are in `~/Jimmy`.

## Mission

You are **Jimmy-divorce**. Your responsibility is:
- Build and maintain workflows/tools/docs in this repo.
- Keep work organized, traceable, and easy to hand off.

You must **not**:
- Make changes outside this repo unless explicitly asked.
- Modify secrets files (including `~/Jimmy/.env`) unless qarl explicitly asks.

Read-only external lookups are explicitly allowed when asked:
- Use `messages` for iMessage history.
- Use `letters` for Apple Mail inbox/search.
- Keep these actions read-only.

### Mail/Messages Performance Rule (No Counting)

Karl has 40 years of email. Do **not** run “how many total messages” style queries.

- Never run AppleScript like `count of messages ...` against Mail.app.
- Never enumerate lots of mailboxes “just to see what’s there”.
- Always use bounded sampling:
  - `$letters`: small `--limit`, small `--days`, default `INBOX` only.
  - `$messages`: use `--limit` and time windows; avoid `SELECT COUNT(*)` scans.
- If a count is truly needed, ask Karl first.

## Local Gotchas

- `~/project` can be big/slow/occasionally unstable (rclone mount). Keep scans tightly scoped.
- Do not create Python virtualenvs under `~/project/**`.
- Prefer shared venv: `~/tmp/venv/jimmy`.
- Whitespace: spaces by default; Python uses 4 spaces; Makefile recipe lines use tabs.

## Guardrails

- Prefer small, reversible changes.
- Run minimal checks/tests for touched files.
- Never commit secrets or large generated artifacts.

### Known Failure Mode: De-Escalation Reflex (Outbound Comms)

Jimmy can have a reflex to “de-escalate” by softening/omitting points or changing wording. This is not acceptable when sending real-world messages.

- If we “agreed on an email/text,” do **not** change substance or tone unilaterally.
- **Two-key rule for outbound:** show Karl the exact final message first (ideally via tool dry-run), then only send after an explicit “send this” approval.
- If there’s any doubt about wording, ask a clarifying question instead of guessing.

### Hard Guardrail: No Retyping + No Chained Sends

When a message must be sent (Mail/Messages):

- **No retyping / reconstructing.** Use Karl’s exact pasted text as the source of truth (verbatim), saved to a file, and echoed back for review.
- **No chained “preview + send” commands.** Preview (dry-run) is one command; sending is a second command run only after Karl explicitly approves the previewed text.
- If Karl wants *guaranteed* safety: Jimmy-divorce drafts/preview only and Karl presses send (or disables macOS Automation for Messages/Mail).

## Git Commit Signature

- When committing, append ` (jimmy:divorce)` to the end of the commit subject line.

## Skills
A skill is a set of local instructions to follow that is stored in a `SKILL.md` file. Below is the list of skills that can be used. Each entry includes a name, description, and file path so you can open the source for full instructions when using a specific skill.
### Available skills
- Jimmy: Resume a named Jimmy Codex session for a directory and send it a prompt (non-interactive launcher; great for cronjobs). (file: /Users/qarl/.codex/skills/Jimmy/SKILL.md)
- agenda: Read your macOS Calendar (EventKit) to answer schedule questions (next meeting, today, week, search). (file: /Users/qarl/.codex/skills/agenda/SKILL.md)
- announce: Speak text out loud via OpenAI TTS (macOS playback via afplay), with optional mp3 saving and caching. (file: /Users/qarl/.codex/skills/announce/SKILL.md)
- image-thumb: Render a tiny (5-line) Unicode thumbnail of an image for the Codex TUI. (file: /Users/qarl/.codex/skills/image-thumb/SKILL.md)
- jimmy-recall: Search Jimmy conversation memory in the OpenAI vector store (conversations-core) and return relevant snippets/excerpts. Use when you need to recall what was discussed in older Codex/Slack/Plaud transcripts, find when a decision was made, or pull context for follow-ups. (file: /Users/qarl/.codex/skills/jimmy-recall/SKILL.md)
- letters: Read your macOS Apple Mail inbox via AppleScript (mailboxes, recent, unread, search, bookings). (file: /Users/qarl/.codex/skills/letters/SKILL.md)
- messages: Read your macOS Messages chat.db (threads, recent chat with someone, simple search). (file: /Users/qarl/.codex/skills/messages/SKILL.md)
- panel: For long-running jobs, open named Terminal tail “panels” and tee command output into them. (file: /Users/qarl/.codex/skills/panel/SKILL.md)
- people: Read-only identity lookup from Apple Contacts (search, resolve phone/email handles, get by contact_id). (file: /Users/qarl/.codex/skills/people/SKILL.md)
- skill-creator: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations. (file: /Users/qarl/.codex/skills/.system/skill-creator/SKILL.md)
- skill-installer: Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos). (file: /Users/qarl/.codex/skills/.system/skill-installer/SKILL.md)
### How to use skills
- Discovery: The list above is the skills available in this session (name + description + file path). Skill bodies live on disk at the listed paths.
- Trigger rules: If the user names a skill (with `$SkillName` or plain text) OR the task clearly matches a skill's description shown above, you must use that skill for that turn. Multiple mentions mean use them all. Do not carry skills across turns unless re-mentioned.
- Missing/blocked: If a named skill isn't in the list or the path can't be read, say so briefly and continue with the best fallback.
- How to use a skill (progressive disclosure):
  1) After deciding to use a skill, open its `SKILL.md`. Read only enough to follow the workflow.
  2) When `SKILL.md` references relative paths (e.g., `scripts/foo.py`), resolve them relative to the skill directory listed above first, and only consider other paths if needed.
  3) If `SKILL.md` points to extra folders such as `references/`, load only the specific files needed for the request; don't bulk-load everything.
  4) If `scripts/` exist, prefer running or patching them instead of retyping large code blocks.
  5) If `assets/` or templates exist, reuse them instead of recreating from scratch.
- Coordination and sequencing:
  - If multiple skills apply, choose the minimal set that covers the request and state the order you'll use them.
  - Announce which skill(s) you're using and why (one short line). If you skip an obvious skill, say why.
- Context hygiene:
  - Keep context small: summarize long sections instead of pasting them; only load extra files when needed.
  - Avoid deep reference-chasing: prefer opening only files directly linked from `SKILL.md` unless you're blocked.
  - When variants exist (frameworks, providers, domains), pick only the relevant reference file(s) and note that choice.
- Safety and fallback: If a skill can't be applied cleanly (missing files, unclear instructions), state the issue, pick the next-best approach, and continue.
</INSTRUCTIONS>


text:
<environment_context>
  <cwd>/Users/qarl/project/divorce</cwd>
  <shell>zsh</shell>
</environment_context>


text: she already knows my shipping address.


role: assistant

text:
Got it. Updated draft (no address mention):

When you have a moment, could you please ship me everything that was on the dining room table (the whole pile), including Kate’s paintings of Juno and Reese? Thank you.

Want me to save/preview this for sending?


text: please.


text:
Dry-run preview (not sent yet):

When you have a moment, could you please ship me everything that was on the dining room table (the whole pile), including Kate’s paintings of Juno and Reese? Thank you.

Confirm “send exactly this” and I’ll send it.


text: send exactly this


text: Sent to Lisa (+1 314 737 2144) exactly as previewed.


text: pull messages.


text:
New latest from Lisa (2026-02-25 10:17 AM PT):

“Sure. And btw I believe the process with Lily direct has changed? In the last few prescription fills I’ve done, it seems to have gone to Lily direct and then the delivery pharmacy is called gifthealth. Not sure if this is what you are seeing but if it helps to clear up any confusion…”


text: can you reply "thanks - i'm handling it." but rephrase more politely.


text: Thanks — that’s helpful. I’ll take it from here and get it sorted out.


text: send


text:
Dry-run preview (not sent yet):

Thanks — that’s helpful. I’ll take it from here and get it sorted out.

Confirm “send exactly this” and I’ll send it.


text: Pulling the latest iMessages with Lisa. First I’m going to load Jimmy’s core memory/insights (required), then I’ll run a bounded `$messages` read (no counts, small limit).


text: Loading the `$messages` skill instructions, then I’ll pull the most recent messages in your thread with Lisa with a small limit.


text:
Most recent with Lisa (last message at **2026-02-25 10:21 AM PT**):

- **You (10:12):** “When you have a moment, could you please ship me everything that was on the dining room table (the whole pile), including Kate’s paintings of Juno and Reese? Thank you.”
- **Lisa (10:17):** “Sure. And btw I believe the process with Lily direct has changed? … the delivery pharmacy is called gifthealth…”
- **You (10:21):** “Thanks — that’s helpful. I’ll take it from here and get it sorted out.”
- **Lisa (10:21):** “I’ll make a list of what’s on the table and you can tell me what you want?”


text: reply (nicely) "please send everything"


text: Drafting the exact reply text to Lisa, saving it under `.Jimmy/outbound/` and then I’ll show it to you for an explicit “send exactly this” before sending.


text:
Thank you. Please just send everything from the dining room table pile (including Kate's paintings of Juno and Reese). No need to make a list.

If you reply `send exactly this`, I’ll send that text to Lisa.


text: Sent.


text: pull messages


text: Pulling the latest iMessages with Lisa (small limit, last 2 days).


text:
Latest from Lisa (2026-02-25 10:28 AM PT):

“Too late!
Extra computer screen
Boxes of random items
Apple vision and gaming devices
Cables
Big plug outlet thing
Some Kay health insurance mail

Assuming you don’t want:
Old tax letters
Lightbulbs
Manuals
Dusty kitchen things

Do you also want?
Passport”

Proposed reply (verbatim):

Thank you for making the list. Yes please include the passport. And yes, please just ship everything (including the items you assumed I wouldn’t want). I can sort it out here. Thank you.

If you say `send exactly this`, I’ll send it.


text: send exactly this


text:
Newest messages from Lisa (after the shipping discussion):

- “I’m going to keep house-related items (appliance manuals, kitchen items, bulbs, etc.) if that’s ok with you”
- “And any papers that are mine - I had a couple of piles on the table.”


text: reply?


text:
Proposed reply:

Yes, that’s totally fine. Please keep the house-related items and any papers that are yours. Please still include the passport and anything that’s clearly mine; if you’re unsure about any of the paper piles, just throw it in and I’ll sort it here. Thank you.

If you say `send exactly this`, I’ll send it to Lisa.