waypoint

Topics in the source

• Waypoint — shell navigational shortcuts
• The one idea that governs everything
• Access constraint (check — don't assume)
• Commands
• Multi-machine scoping
• Launch aliases (the second managed block)
• Window layouts (Space + bounds per focus window)
• Common requests → what to do

Waypoint lets the user refer to active project roots by name: as environment variables ($NOTES, $THESIS) and as a one-word jump command (wp thesis). The CLI is a single self-documented Python 3 script (stdlib only, no dependencies), tools/waypoint/waypoint in its repo, linked as /.config/waypoint/waypoint. Its tables live in the data directory, $WAYPOINTDATA or /.config/waypoint (often a symlink into a private synced repo); waypoint path prints every location. The database is the source of truth; the shell file is a rendered copy. Database: /.config/waypoint/waypoints.md — a GFM table (Name | Path | Added | Status | Notes | Machine). Editing this table (by hand or via commands) then running sync is how the system changes. Rendered output: a single fenced block in the user's /.zshrc, between # >>> waypoint (managed …) >>> and # >> waypoint (managed' /.zshrc up front. Match the sentinel precisely like that: the looser '>>> waypoint' also matches the waypoint-launch sentinel, so it reports 2 on a perfectly healthy file. Sometimes the bash tool runs in a VM whose $HOME isn't the user's, so /.zshrc is invisible and sync is the user's to run. But in other setups ($HOME=/Users/ ) you can

This is an excerpt. Refer to the complete source and its current requirements.