> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_31/session_04_extensions_and_agent_routes.md). # Session 04: Extensions And Agent Routes **Session ID**: `phase31-session04-extensions-and-agent-routes` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Bring each registered extension and agent surface into safe read-only or browser-local demo behavior. *** ## Scope ### In Scope (MVP) * Force Hermes, Claude Code, OpenClaw, and Knowledge Graph routes into existing or new demo/read-only modes. * Ensure Hermes and OpenClaw do not fetch tokens, chat, uploads, missions, documents, file previews, dashboard bridges, or admin status/actions. * Make Trend Finder trends, workbench, hidden gems, sources, watchlist, brief, and engine replay read from snapshot data or fixture/demo fallbacks. * Replace Trend Finder asset bridge URLs with `/demo/trend-finder-assets/*` or unavailable states. * Ensure Trend Finder source setup and scheduler status controls use snapshot state with `autoLoad: false`. * Verify AI Rogue Play, Ledger, Loadout, and Settings use bundled assets, browser-local persistence, and no bridge, remote loader, server state, or private telemetry call. * Add focused route tests for representative agent, Trend Finder, Knowledge Graph, and AI Rogue paths. ### Out of Scope * New extension capabilities beyond demo-safe behavior. * Default AI Rogue enablement outside public demo mode. * Hosted collection, scraping, scheduler, local-agent control plane, upload, or admin-write work. * New public source adapters or source-compliance decisions. *** ## Folded Source Details Extension and agent endpoint groups to avoid: * Trend Finder: `/__run_trend_finder`, `/__run_trend_finder_status`, `/__trend_finder_source_setup`, `/__trend_finder_scheduler_status`, `/__trend_finder_creator_lens`, `/__trend-finder-visibility-config`, `/__trend_finder_asset/*`. * Knowledge Graph: `/__graphify_list`, `/__graphify_graph`, `/__graphify_admin_status`, `/__graphify_ingest`, `/__graphify_remove`. * Hermes: `/__hermes_*`, including `/__hermes_chat`, `/__hermes_image_upload`, `/__hermes_missions/*`, `/__hermes_documents*`, and `/__hermes_obsidian`. * OpenClaw: `/__openclaw_*`, including `/__openclaw_admin_status` and `/__openclaw_admin_action`. Route behavior matrix: * Knowledge Graph: use public graph snapshots/demo fixtures; disable ingest/remove and live polling. * Hermes Agent: force demo/read-only route; no token, chat, upload, missions, documents, file previews, or admin writes. * Claude Code Agent: force demo/read-only route; no local process assumptions or live-mode toggle. * OpenClaw Agent: force demo/read-only route; no dashboard bridge, token, or admin actions. * Extensions index: show every registered extension as enabled in public demo mode. * Trend Finder Trends: render curated frozen trend report with explicit snapshot labels. * Trend Finder Workbench: read from snapshot; browser-local filters and visibility toggles are allowed only when clearly local to the browser. * Hidden Gems: read from snapshot. * Sources: show source states/provenance from snapshot; no source setup writes or scheduler status polling. * Watchlist: read-only generated demo watchlist. * Brief: read-only handoff view. * Engine Replay: show sanitized latest-run trace or fixture trace; no raw logs or asset bridge calls. * AI Rogue: include Play, Ledger, Loadout, and Settings with bundled assets and browser-local persistence only. Trend Finder labels must clearly distinguish frozen snapshot, fixture/demo data, deterministic fallback, and redacted generated source snapshot as appropriate. Future registered extensions must be visible in the demo, with unsafe actions rendered read-only, unavailable, or browser-local. *** ## Prerequisites * [ ] Sessions 01 through 03 are complete. * [ ] Snapshot fixtures include enough data for Trend Finder, Knowledge Graph, host routes, and demo agent surfaces. * [ ] AI Rogue browser-local persistence remains scoped to public-safe browser state. * [ ] Existing route-level demo modes for Hermes/OpenClaw/Knowledge Graph are identified before adding new logic. *** ## Deliverables 1. Demo-safe route behavior for all current registered extensions and agent pages. 2. Static asset URL handling for Trend Finder demo assets. 3. Focused route tests for representative agent, Trend Finder, Knowledge Graph, and AI Rogue paths. 4. Clear data labels for frozen snapshot, fixture/demo, deterministic fallback, unavailable, and browser-local states. 5. No-bridge coverage for the endpoint groups listed above. *** ## Success Criteria * [ ] Every route listed in the feature matrix is reachable in demo mode. * [ ] Trend Finder pages label data as frozen snapshot, fixture/demo data, deterministic fallback, or redacted generated source snapshot as appropriate. * [ ] AI Rogue state remains browser-local and does not leak host or private runtime information. * [ ] Knowledge Graph, Hermes, Claude Code, and OpenClaw do not contact any local bridge or admin endpoint in demo mode. * [ ] Future registered extensions have a visible demo-mode rule to follow. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_31/session_04_extensions_and_agent_routes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.