From fdb61ed010cc28b3dd4717c99a1c06dc171c301b Mon Sep 17 00:00:00 2001 From: Ajax Davis Date: Fri, 16 Jan 2026 14:06:36 +1000 Subject: [PATCH] docs(web): add viewing parent updates documentation Document how users can view the parent agent/collection to see: - Current tools and collections the parent has - How to manually update fork with parent changes - API endpoint for fetching parent data programmatically --- apps/web/src/app/docs/platform-guide/page.tsx | 98 +++++++++++++++++++ 1 file changed, 98 insertions(+) diff --git a/apps/web/src/app/docs/platform-guide/page.tsx b/apps/web/src/app/docs/platform-guide/page.tsx index 442b6d9..3cf5587 100644 --- a/apps/web/src/app/docs/platform-guide/page.tsx +++ b/apps/web/src/app/docs/platform-guide/page.tsx @@ -50,6 +50,7 @@ const NAV_SECTIONS = [ { id: 'fork-agents', label: 'Fork Agents' }, { id: 'fork-collections', label: 'Fork Collections' }, { id: 'fork-attribution', label: 'Attribution' }, + { id: 'viewing-parent-updates', label: 'Viewing Parent Updates' }, ], }, { @@ -1260,6 +1261,103 @@ Always cite your sources and be transparent about limitations.`} + +

+ After forking, you can check what the original parent has changed by visiting + its page. This lets you see new tools or collections the parent author has added. +

+ +
+

+ 1. Go to your forked agent or collection in the dashboard +

+

+ 2. Click the "Forked from" badge to navigate to the parent +

+

+ 3. The parent's page shows its current tools and collections +

+

+ 4. Compare with your fork to see what's different +

+
+ + +

+ When you visit the parent, you'll see its current state: +

+
+
+

For Agents

+
    +
  • • Current attached tools
    • +
  • • Current collections
    • +
  • • Updated system prompt
    • +
  • • Model and provider changes
    • +
  • • Temperature and settings
    • +
+
+
+

For Collections

+
    +
  • • Current tools in collection
    • +
  • • Tool order and positions
    • +
  • • Updated description
    • +
  • • Newly added tools
    • +
  • • Removed tools
    • +
+
+
+ + +

+ TPMJS uses a manual update model—your fork doesn't automatically sync with + the parent. To incorporate parent changes: +

+
+

+ 1. View the parent's current tools/collections +

+

+ 2. Go to your fork's edit page +

+

+ 3. Manually add or remove tools to match (or improve upon) the parent +

+

+ 4. Update settings as needed +

+
+
+

+ Note: This manual approach gives you full control over what + changes to accept. You can cherry-pick specific updates without taking + everything the parent has changed. +

+
+ + +

+ You can also fetch parent information via the API: +

+ + + + {/* ==================== API KEYS ==================== */}