Repository navigation
feat(routines): graph workflows group topics under broader ones - #594
Merged
Merged
Conversation
The Find what to tidy node gets a cluster kind: topics whose labels end in another topic's label go under it, and three or more with no broader topic that end in the same word go under a new topic for it. Ask the model checks each group, and Apply changes makes the sure ones and proposes the rest. Undoing a group takes its topics out from under the broader one, and deletes that topic when the group made it and nothing has used it since. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Nbf5G7PvMgThj8BbUPGT8
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: graph workflows could merge, link, retype and hide entities (#567), but topics stayed a flat list unless someone set each one's broader topic by hand. "Sales calls", "Support calls" and "Team calls" sat side by side with nothing above them.
After: the Find what to tidy node has a third new kind in Look for, Topics to group (
cluster):Ask the model checks each group (it can rename the new topic or leave some out), and Apply changes makes the sure ones and proposes the rest. In Routines › Proposed changes a group shows as "Group under a new topic, “Calls”?" with its topics, Group them, Leave them and Undo.
POST /graph-changes/{id}/accepttakeslabelto name the new topic. Undo takes the topics out from under it and deletes the topic when the group made it and nothing has used it since.No built-in workflow or routine changes: nothing is grouped until someone adds a workflow that looks for topics to group.
Motivation and Context
The last part of the parked "More graph cleanup nodes" item (DEVLOG: "More graph nodes: retype entities, hide noise, cluster topics"), following #567.
How
organize.pygetstopic_groups(rules A and B above, keyscluster:<space>:<parent>so a dismissed or undone group isn't found again), a cluster judge schema (agree,label,leave),_make_groupwithtopics.create/topics.update, and_ungroupfor undo. Topics aren't in graph history, so a group is undone from its graph change only.Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.changelog.d/. (n/a: the title says it)Done questions (AGENTS.md)
label), dismissed and undone with/api/v1/graph-changes, andundo_graph_changeover MCP.make openapi).topics.create/update, the graph change flow and the judge from feat(routines): graph workflows find wrong types and noise to tidy #567.Local CI (
ci/local-ci.sh): backend (embedded SurrealDB), Next.js, pre-commit, title and upgrade pass. The SurrealDB server job lost its server mid-run (handshake timeouts across unrelated tests, which this container does when jobs share its cores); GitHub CI decides it.Generated by Claude Code