From 0d73e36ad4db57796b97fab30388fdba5cb17208 Mon Sep 17 00:00:00 2001
From: Amolith <amolith@secluded.site>
Date: Wed, 18 Mar 2026 22:54:28 -0600
Subject: [PATCH] Document dev server command in AGENTS.md

---
 AGENTS.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/AGENTS.md b/AGENTS.md
index f727844dff1cd5ab55a0c4f8f80def035cd2c7c4..4a54a07cc8f017221c1fbbf9929ff2e51392667e 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -12,6 +12,7 @@
 - Format: `jj fix` (rustfmt via repo-level jj config)
 - Lint (warnings are errors): `cargo clippy --quiet -- -D warnings`
 - Verify after changes: `make verify` (formats, typechecks, lints, and tests in one pass)
+- Dev server example with custom fish script to listen on a random, unused, unprivileged port over tailscale: `PORT=$(fish -c random_free_port) cargo watch -x "run -- webui --host $(ts ip -4) --port $PORT"` (user might not actually use fish or ts, check first and don't offer if they don't use either)
 
 ## Implementation details
 - Project resolution: most commands resolve the project via `db::resolve_project_name()` which checks `--project` flag, `TD_PROJECT` env var, or the directory binding in `~/.local/share/td/bindings.json`. Without a resolved project, commands fail with "no project selected". Only `project` and `skill` subcommands avoid this check.