@@ -26,7 +26,7 @@ When I provide the URL to or number of a ticket, todo, or issue, use the appropr
## Notify me when you're finished
-If I've asked you to ntfy me when you're done or if you ever have any questions at all, please send a notification by using `ht` to POST to `https://ntfy.sh/$NTFY_TOPIC_LLM` with `-A bearer -a $NTFY_ACCESS_TOKEN`. Set the following headers:
+If I've asked you to ntfy me when you're done or if you ever have any questions at all, please send a notification by using `ht` to POST to `https://ntfy.sh/$NTFY_TOPIC_LLM` with the token in the `Authorization` header. Set the following headers:
- **t**(itle): brief, informative, sentence-case summary of what you did (e.g. "Refactored authentication middleware in rumilo")
- **ta**(gs): comma-separated emoji shortcodes (prefer to use one). Must be a _valid_ shortcode (moss and seahorse aren't valid) or it'll be treated as a text tag instead of an emoji prefix.
@@ -39,36 +39,40 @@ If `$SHELLEY_CONVERSATION_ID` is set, find this conversation's slug with `sqlite
For example
```bash
-ht POST "t:" "ta:" "" # normal example-ht POST "t:" "ta:" "" Click:https://vm-host.shelley.exe.dev/c/some-slug # from shelley-# link to something i might plausibly have asked for-# slightly more urgent example saying the disk is full or something
# normal success, not from Shelley
-ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" -A bearer -a "$NTFY_ACCESS_TOKEN" \
+ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" \
+ "Authorization:Bearer $NTFY_ACCESS_TOKEN" \
"t:Refactored authentication middleware in rumilo" \
- ta:hammer_and_wrench \- "Shitty coding agent (pi) finished refactoring the auth middleware in rumilo. Session validation is cleaner now and all tests pass."
+ "ta:hammer_and_wrench" <<'EOF'
+Shitty coding agent (pi) finished refactoring the auth middleware in rumilo. Session validation is cleaner now and all tests pass.
+EOF
# from Shelley, with click URL to the conversation
-ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" -A bearer -a "$NTFY_ACCESS_TOKEN" \
+ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" \
+ "Authorization:Bearer $NTFY_ACCESS_TOKEN" \
"t:Added HEIC upload support in shelley" \
- ta:white_check_mark \- Click:https://vm-host.shelley.exe.dev/c/heic-upload-support \- "Shelley finished adding HEIC-to-JPEG conversion for image uploads in shelley. The new imageutil helper handles it transparently and tests cover the happy path."
+ "ta:white_check_mark" \
+ "Click:https://vm-host.shelley.exe.dev/c/heic-upload-support" <<'EOF'
+Shelley finished adding HEIC-to-JPEG conversion for image uploads in shelley. The new imageutil helper handles it transparently and tests cover the happy path.
+EOF
# linking to something relevant, not from Shelley
-ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" -A bearer -a "$NTFY_ACCESS_TOKEN" \
+ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" \
+ "Authorization:Bearer $NTFY_ACCESS_TOKEN" \
"t:Updated AUR package for kagi-ken" \
- ta:package \- Click:https://aur.archlinux.org/packages/kagi-ken \- "Crush finished bumping the kagi-ken AUR package to v0.4.2 and updated the checksums."
+ "ta:package" \
+ "Click:https://aur.archlinux.org/packages/kagi-ken" <<'EOF'
+Crush finished bumping the kagi-ken AUR package to v0.4.2 and updated the checksums.
+EOF
# something went wrong
-ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" -A bearer -a "$NTFY_ACCESS_TOKEN" \
+ht POST "https://ntfy.sh/$NTFY_TOPIC_LLM" \
+ "Authorization:Bearer $NTFY_ACCESS_TOKEN" \
"t:Build failed in pi-mono — disk full" \
- ta:rotating_light \- p:4 \- "Amp ran into a full disk on the build server while compiling pi-mono. /var/log looks like it needs rotation. The build is blocked until there's space."
+ "ta:rotating_light" \
+ "p:4" <<'EOF'
+Amp ran into a full disk on the build server while compiling pi-mono. /var/log looks like it needs rotation. The build is blocked until there's space.
+EOF
```
## Planning before acting