Repository navigation
Refresh README for automations, reminders, variables, and MCP - #253
Open
steezeburger wants to merge 4 commits into
Open
steezeburger wants to merge 4 commits into
steezeburger wants to merge 4 commits into
Conversation
These are the most-used features day to day, but the README still framed automations as "where it's headed" even though triggers, the query DSL, the verb vocabulary, for:: iteration, and variables are all shipped. Give automations, reminders, and variables their own sections with real syntax examples, and trim "Where it's headed" down to what's actually still unbuilt (the reactive slice, action chaining, webhooks, the widget layer).
Fact-checked the prior rewrite against the actual code and fixed three real bugs it introduced: `weekly tue,thu 5:30` isn't valid syntax (the weekly cadence only takes one weekday — switched the headline example to the `cron` escape hatch, which does support a multi-day dow field); `notify "..." on match` silently ignores "on match" (notify only reads its first arg) rather than gating on it; and `for:: 1..5` doesn't parse without an explicit `by <step>`. Also corrected the MCP tool count (16 → 18, counted from mcp_server/tools.py's registry) and clarified the `every` cadence's actual `Nm`/`Nh` syntax. The five in-flight issues the prior session flagged as still unmerged (#206, #217, #225, #236, #250) are all still open on main, so "Where it's headed" needed no changes. Added three real screenshots (docs/images/screenshot{4,5,6}.png), taken against a locally-bootstrapped instance (no Docker daemon in this sandbox, so used the .ai/PROJECT_SETUP.md hybrid fallback) with seeded example content matching the README's own prose: the corrected automation block, the Overdue saved view embedded on a page, and the chat panel mid-conversation running a query tool. Skipped the Discord reminder screenshot since no webhook is configured in this sandbox and faking one didn't seem worth it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018yMA39rVbEJzFYZvH8mQCZ
Vertical padding on an inline element doesn't grow its line box, so on multiline content where a highlighted chip sits at the start of every line (a multi-property automation definition: trigger::/query::/ action::), adjacent chips' backgrounds visually touched with no gap, reading as one connected block instead of separate lines. Giving .inline-tag and .inline-property-value their own taller line-height grows just the line box they're on, without affecting ordinary prose lines that don't contain a chip. Re-captured the three README screenshots against the fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018yMA39rVbEJzFYZvH8mQCZ
Owner
Author
|
Deploy to Staging failed (exit 137, OOM-killed mid- I added Generated by Claude Code |
…ase properties, drop chat screenshot - Swap the line-height increase for a smaller vertical padding on .inline-tag/.inline-property-value. Growing line-height also widened the gap around ordinary text on any line that mixed prose with a chip; shrinking the chip's own box instead leaves normal text spacing untouched and only opens up room between stacked chips. - Replace the automation query example's `tag:priority` with `prop:priority=high` (and the matching `priority:: high` property on the seeded Roadmap todos, replacing the #priority tag) — better showcases the property query predicate, which the feature is more distinctively about than a plain hashtag. - Drop the in-app-chat screenshot; that section doesn't need the same visual emphasis as automations/reminders/variables/MCP. Re-captured screenshot4/5 against these changes; screenshot6 removed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018yMA39rVbEJzFYZvH8mQCZ
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes automations into their own section with real, verified syntax (trigger cadences, query DSL, verb list,
allow::,for::), splits reminders out from scheduling, adds a Variables section for{{token}}syntax and custom variables, and lightly touches up MCP. All examples were fact-checked against the current code (automation_spec.py,automation_actions.py,content_tokens.py,mcp_server/tools.py) and three real screenshots were added and referenced inline, captured against a locally-bootstrapped instance.Also fixes a small CSS bug noticed along the way:
.inline-tag/.inline-property-valuechips had no line-height headroom, so a multiline#automationblock (a chip at the start of every line) rendered as one visually-connected block instead of separate lines.🤖 Generated with Claude Code
https://claude.ai/code/session_018yMA39rVbEJzFYZvH8mQCZ
Generated by Claude Code