feat(calendar): add advanced event search - #218
Open
dtump wants to merge 1 commit into
Open
Conversation
dtump
force-pushed
the
feat/advanced-calendar-search
branch
from
July 30, 2026 12:42
eef9769 to
51d53c9
Compare
Signed-off-by: Dick Tump <dick@tump.me> Assisted-by: Codex:gpt-5.6-sol
dtump
force-pushed
the
feat/advanced-calendar-search
branch
from
July 30, 2026 12:56
51d53c9 to
e3510a0
Compare
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
1 participant
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.
Closes #216.
I built this because I wanted Assistant to answer calendar questions more reliably, for example:
This adds a separate, read-only
Calendar: Advanced Searchcategory. It searches a required, bounded date range across the current user’s event calendars, expands recurring events and exceptions, supports grouped content matching, and reports incomplete or truncated results explicitly.I kept it separate from
calendar.pybecause the implementation is substantial and it reads full event resources inside Context Agent for recurrence and content matching. The separate category lets admins enable or disable that access independently. Only bounded selected fields are returned to the LLM; descriptions can be matched locally but are not returned. I am happy to adjust the structure if maintainers prefer another approach.Validated against Context Agent 2.7.0 and current main, with 27 synthetic tests in a separate development harness, the upstream Ruff, Black and isort configuration, and a live Nextcloud test. Because this repository currently has no Python unit-test setup, I did not introduce one solely for this PR. I hope that is okay.
The implementation and test hardening received material AI assistance. I did functional testing myself.
Screenshot because the proof is in the pudding:
