Skip to main content
The AI only knows where you are in Stage when it can read the current page context. If there is no context, it cannot create, rename, or edit anything safely. This page explains what “context” means and how to make sure the chat sees it.

​
What is Page Context?

“Context” is a snapshot of the entity you are viewing—Core, Blueprint, Activity Guide/Form, or SOP—plus its related IDs. The assistant relies on that snapshot to route requests to the correct tool. Without it, every action would be a guess.

Entity

Core, Blueprint (category), Activity, Guide/Form, or SOP content.

Metadata

Includes entity ID, parent Core/Process IDs, current version info, and content type.

​
How Context is Detected

Context comes from the page-context-detector.ts helper. It watches the current URL and Inertia props and sets entity_type, entity_id, related core/category IDs, and any open content version. The detector only fires when you are on pages it understands:
1

Core pages

/business-processes/{processId}/cores/{coreId} — required for creating or renaming cores and for selecting blueprints/activities in chat.
2

Blueprint pages

/blueprint/category/{categoryId} — needed before adding activities or blueprints and for blueprint SOPs.
3

Guide/Form pages

/content/guide|form/... — required before creating or editing activity guides, forms, or SOP versions.
If you are elsewhere (dashboard, list view, modal-only screens), the detector returns null and the AI can only answer generic questions.

​
Why You Must Open the Right Page First

The chat does not auto-detect what you’re referencing. Navigate to the Core, Blueprint, or Guide page first so the assistant can capture the IDs and version metadata.
Being on the correct page ensures:
  • Accurate actions – commands like “rename this core” or “add an activity here” map to the open entity.
  • Safer edits – SOP updates target the current version tied to the page.
  • Relevant data – RACI lookups, blueprint listings, and activity queries only run inside the loaded core.

​
Troubleshooting Missing Context

SymptomLikely CauseFix
Chat replies “Please navigate to a Core/Blueprint page”Detector returned null.Open the Core, Blueprint, or Guide page and retry.
AI says it can’t find IDs or permissionsYou’re on a list/dashboard view.Drill into the entity detail page before asking.
SOP tools ask for navigation even though you’re editingViewing an embedded editor without the main page loaded.Refresh and open the full entity page so the version info loads.
If you switch tabs or open multiple cores at once, reload the page before giving new instructions so the context detector can update.

​
Quick Checklist

  • ✅ Open the Core, Blueprint, Activity, or Guide page you want to work on
  • ✅ Confirm the chat badge shows “Context available” (blue icon)
  • ✅ Then ask the AI to create, rename, or edit
When in doubt, navigate first—context is the AI’s map.