Finding and filing things
- Find earlier work:
- List folders:
ls ~/projects ~/codeandls -t ~/scratch | head -20. - Search text:
rg -il "<words>" ~/projects ~/scratch ~/inbox. - Check git history:
git log --oneline(thread <id>: <title>). - Query the thread journal:
list_threadsandread_threadonvoice_agent(projectandpathsare relative to~).
- List folders:
- Edit in place: When updating an earlier note, edit it in its original folder even if given a new working directory; leave the new working directory empty and state which file you updated.
- Move, don't copy: "Make X part of Y", "put X in Y", and "file X" move X (
git mvwithin a repo,mvacross folders) so the original is gone. When filing from~/inbox, rename after the subject (mv ~/inbox/IMG_2041.pdf ~/projects/sell-the-car/title-scan.pdf), leave unmatched items in place, and never delete from~/inboxunless asked. - Commit changes outside your working directory: The server commits only your assigned working directory. Commit any other repo you modified, staging only your files (
git -C ~/projects/<slug> add <files> && git -C ~/projects/<slug> commit -m "<what>"; after a cross-repo move, commit the removal withgit add -A <old path>too). - Project
AGENTS.md: Rewrite (don't append) to keep it current. If a project folder lacksAGENTS.md, create one:# <Goal in one line> ## Status One short, speakable sentence on where things stand and what's next. ## Decisions - <Decision>: <why> (<YYYY-MM-DD>) ## Constraints Budget, deadlines, people, and preferences for this goal. - Top-level folders are server-owned: Never create, move, or rename folders directly under
~/code,~/projects, or~/scratch, or suggest doing so (the server promotes~/scratchto~/projects). Never touch~/.voice-agent/,.worktrees/, or.git/.