docs: consolidated filesystem sync trigger docs (agents + workforces)#655
Draft
jordanc-relevanceai wants to merge 4 commits into
Draft
docs: consolidated filesystem sync trigger docs (agents + workforces)#655jordanc-relevanceai wants to merge 4 commits into
jordanc-relevanceai wants to merge 4 commits into
Conversation
Create a new page for filesystem sync triggers explaining how file writes to project memory or personal files volumes automatically trigger agents, including glob pattern filtering, 100KB content limit, conversation threading behavior, and access controls. Update triggers.mdx overview and docs.json navigation to include the new trigger type. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add filesystem sync trigger type to the triggers overview and configuration sections, and add a brief description to the trigger-to-agent-configuration types list. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…filesystem-sync-triggers # Conflicts: # docs.json
…filesystem-sync-triggers
This was referenced Jun 3, 2026
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
This PR consolidates 2 drafter PRs that both document the filesystem sync trigger feature, in two different surfaces. Opened as draft for review before the source PRs are closed.
Source PRs (being closed in favor of this one)
Why consolidated
Both PRs document the same feature — filesystem sync triggers — just from the agent side (#613) and the workforce side (#631). Shipping them together keeps the terminology, glob-pattern examples, and behavior notes consistent across the two trigger surfaces instead of drifting apart in separate merges.
Changes by source PR
#613 — TSP-1227 (agents)
build/agents/build-your-agent/agent-triggers/filesystem-sync.mdxcovering watched volumes (shared memory vs personal files), glob pattern filtering, the 100KB content limit, conversation threading, and access controls.triggers.mdxoverview to include filesystem sync in the trigger types section and decision table.docs.jsonunder Trigger Types.#631 — TSP-1245 (workforces)
build/workforces/build-an-ai-workforce/add-triggers.mdx— overview, use cases, and a numbered configuration walkthrough with glob pattern examples.trigger-to-agent-configuration.mdx.Reconciliation note
docs.jsonwas rebuilt on top of currentmain(the agent-triggers nav group had been reorganized andsdk-and-api-triggersrenamed toapi-triggersince these branches forked), so the only nav change here is the single newfilesystem-syncentry.