Repository navigation
feat(automations): match trees for conditions - #425
Merged
Merged
Conversation
One condition language for the workflow studio (docs/automations.md, Match trees): all, any and not over the workflow engine's tests, with a check that names the first problem and where it is, depth and size caps, and a reading in words. Condition, filter and switch nodes take a tree in `match` as well as one test; graphs saved before run unchanged. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RFQUkVmALkdhRqXY1yFxW5
16 of 22 tasks
adeelahmad
added a commit
that referenced
this pull request
Oct 15, 2026
… in progress (#430) The stream of activities (#425 to #428) merged: agents read it through the API, MCP's timeline tool and the assistant. Say so under Automate it, with automations that act on it labelled in progress, add the open Settings section (#429) to In progress, and link the automations page from the docs index. Claude-Session: https://claude.ai/code/session_01HDx7PPUauyjMn1LZs8JAsS Co-authored-by: Adeel Ahmad <noreply@anthropic.com>
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.
Requested by Adeel · project thread
Description
Before: a workflow's condition, filter and switch nodes could test one thing (
{path, op, value}), and there was no shared condition language for the workflow studio's triggers.After: one condition language, match trees (
app/domain/match.py):all,anyandnotover the same tests the workflow engine already has.match.checknames the first problem and where it is (the condition, all.1.not: compare with a number), trees nest at most 6 deep with at most 50 tests, andmatch.describereads a tree in words. Condition, filter and switch cases take a tree inconfig.matchas well as one test; graphs saved before run exactly as they did.How: the leaf tests reuse
flow.test, andflow.check_testnow builds on a newflow.test_problem, so the leaf rules live in one place. This is the first part of workflow studio module M1 (event contract and stream core); triggers, an automation's If and the event stream build on it next.Motivation and Context
Workflow studio plan (
/mnt/project-files/workflow-studio/plan.md, section 3.6 and brief M1 step 4).Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.## UnreleasedinCHANGELOG.md. (n/a: the title says it)Done questions (AGENTS.md)
matchis an optional new config key.tests/domain/test_match.py; docs/automations.md, processing.md, mkdocs nav. No generated files change.flow.testand the same checks, not a copy.🤖 Generated with Claude Code
https://claude.ai/code/session_01RFQUkVmALkdhRqXY1yFxW5
Generated by Claude Code