[bashhack]

sesh is now released and in daily use (Homebrew), while it's still developed on the same computer. This makes keeping the two apart one command, and writes down how to work on sesh, for people and coding agents.

• scripts/sesh-dev builds the checkout to build/sesh-dev (git-ignored) and runs it with SESH_DB_PATH, SESH_AUTH_SOCK and XDG_CONFIG_HOME in SESH_DEV_DIR (default ~/.local/share/sesh-dev), and without a sync or backup folder inherited from the shell. Tried with a throwaway SESH_DEV_DIR: the vault, its backup and the config path were all inside it, and sync was off.
• AGENTS.md: the daily sesh and the dev sesh, and why they mustn't share an agent; the rules for coding agents (throwaway folders, no clipboard, no touchid enable / browser install unless asked, stop what you start); what the two still share (the browser extension's helper script, the agent's log, the clipboard, ~/.aws); trying a dev build as the daily sesh (brew unlink / brew link); building and testing (touched packages, the race setting CI uses, hooks); one-line commits, staging by name, the untracked plan docs; releasing.
• It also says that, since v0.1.0, a vault a released sesh made must keep opening in later ones.
• README's Development section and scripts/README.md point to it.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!