Application Context

Application Context is a property-level workspace for collecting and maintaining structured context about your application. Use it to bootstrap context for a property, monitor live findings as they arrive, edit entries manually, and restore an earlier version when you need to roll back changes.

01When to use Application Context

Use Application Context when you need a shared, current source of truth for a property. It is especially useful when you want to capture important details quickly, review context as new findings appear, or correct and refine context manually over time.

Common use cases include:

• Bootstrapping context for a new property before your team starts deeper work
• Reviewing live findings while context collection is still in progress
• Cleaning up or expanding entries after automatic collection finishes
• Restoring a previous version if recent edits or findings introduce unwanted changes
• Keeping property information organized in a dedicated place instead of spreading it across notes or tasks

02Core concepts

Property context entries

Application Context stores information as structured entries attached to a property. Each entry lives inside a section, so you can organize knowledge by area instead of managing one flat list.

Use entries to capture durable property knowledge such as product areas, integrations, workflows, user roles, operational notes, or environment-specific details. Add entries during bootstrap or create and revise them manually whenever you need to clarify wording, fix incorrect details, or document something that was not captured automatically.

Live findings and bootstrap lifecycle

When you start a bootstrap flow, Application Context begins gathering context for the property with an AI-powered workflow. The page shows live progress while the run is active, so you can watch findings arrive, see which areas are being explored, and confirm that collection is moving forward.

Bootstrap collection is useful when you want to generate an initial knowledge base quickly. As findings appear, review them for coverage, note missing areas, and plan any cleanup or follow-up edits after the run completes.

Versions and restore points

Application Context keeps versions so you can track how property context changes over time. New versions reflect bootstrap results and manual edits, which gives you restore points when you need to roll back to an earlier state.

Use version history to review how the context evolved, recover from unwanted edits, or restore a known-good snapshot before making larger changes.

03Manage application context

Bootstrap context for a property

Open the property you want to update, then select the Application Context tab from the property navigation. If the property does not have context yet, use the empty state to start generating context automatically.

Start bootstrap when you want Canary to create an initial structured context for the property. The generation flow gathers information automatically and streams live progress back into the page, so you can monitor activity without leaving Application Context.

After bootstrap starts, stay on the Application Context tab to watch live findings and status updates as they arrive. Use this view to confirm progress, identify gaps early, and decide what you want to refine after generation finishes.

Review and edit entries manually

After bootstrap finishes, review the broader property view to understand what Canary has already discovered. Use the graph-oriented layout to inspect structured entries alongside richer property-level surfaces for access contexts, open exploration work, unanswered questions, readiness and state signals, and campaign controls.

Review each section and update anything that needs clarification. Add a new entry when knowledge is missing, open an existing entry to edit its content, or remove entries that no longer belong in the property context.

Use manual editing to turn generated context into a reliable reference for your team. Keep entries concise, move information into the right section, and update wording so each section stays easy to scan and maintain.

Track collection progress and findings

Use the property view while bootstrap and follow-up discovery runs are active to follow progress in real time. This view helps you see what Canary is discovering, which access contexts are already mapped, what exploration work is still open, and where unanswered questions remain.

Review the graph surfaces as findings arrive so you can tell whether the property is ready for deeper work or still needs more discovery. If findings look incomplete or unexpected, wait for the current run to finish, then update entries manually or plan another round of collection.

Organize context into sections

Use sections to group related entries inside Application Context. Organize sections around how your team reviews application knowledge, such as product surfaces, integrations, authentication, environments, or operational concerns.

Create sections before adding new entries when you want a clear structure from the start. If bootstrap generates useful information but the layout needs work, move or edit entries so each section stays focused and easy to review.

The following table shows common ways to organize sections:

Section type	Use it for
Product areas	Core features, pages, user journeys, and business flows
Integrations	Third-party services, dependencies, and external systems
Authentication and access	Login methods, roles, permissions, and account requirements
Environments and operations	Environment-specific details, setup notes, and operational considerations
Team knowledge	Known limitations, conventions, and important context your team wants to preserve

Restore an earlier version

Open version history from the Application Context page to review previous versions and restore an earlier state when needed. Use this history to inspect changes from bootstrap runs and manual edits before you decide to roll back.

Version history is useful when a recent edit introduces mistakes, a generated update changes too much, or you want to compare the current context against an earlier snapshot. Review the available versions carefully, then restore the version that matches the state you want to recover.

04Best practices

• Bootstrap context first when you are setting up a new property or refreshing stale information
• Review live findings during collection so you can spot gaps or unexpected results early
• Edit entries manually to improve clarity, fill in missing details, and remove outdated information
• Restore an earlier version instead of trying to manually undo large unwanted changes
• Keep Application Context focused on durable property knowledge that your team will reuse
• Revisit context regularly so it stays aligned with changes in your application

05How Canary uses application context

Canary uses Application Context as maintained property knowledge that can inform exploration, review, and workflow execution. When your property context is current and well-structured, Canary can use it to understand important parts of your application more consistently.

Workflow agents can now use pre-run guidance derived from your application knowledge graph before a run begins. This guidance helps agents start with better context about product structure, terminology, roles, integrations, and other durable property knowledge already maintained in Application Context.

Use Application Context to improve pre-run guidance quality over time. When you correct unclear entries, add missing sections, or keep terminology aligned with how your team describes the application, you give workflow agents stronger context before they start executing a workflow.

06Managing and improving context

Treat Application Context as a maintained source of truth for each property, not a one-time bootstrap artifact. Keep sections organized around durable knowledge your team and Canary reuse across runs.

Use the following practices to improve context quality and make pre-run guidance more useful for workflow agents:

Practice	Why it helps
Keep terminology consistent	Gives workflow agents clearer pre-run guidance about names your team uses for pages, flows, roles, and systems
Update entries after product changes	Keeps property knowledge aligned with the current application before the next workflow run starts
Add missing operational or access details	Helps Canary understand login requirements, roles, dependencies, and environment differences earlier
Remove outdated or duplicate entries	Reduces confusing guidance and keeps the maintained knowledge graph easier to trust
Review version history before large changes	Lets you refine context confidently and restore an earlier snapshot if a revision makes the property knowledge less useful

When workflows depend on nuanced product terminology or app-specific structure, revisit Application Context before running them at scale. Small improvements to maintained property knowledge can produce better execution context before agents begin a run.

07Related

Use these related docs when you want to connect property context review with the rest of your team workflows or move from structured context into graph exploration:

• Knowledge Graph
• Properties
• Agent Tasks
• Workflows
• API Sequences
• Versions

Use Knowledge Graph when you want to explore discovered concepts in the full-screen graph workspace, browse the Explore view, inspect concept details, or manage ongoing discovery controls beyond the core Application Context workflow.

Use Workflows when you want to understand how workflow agents use pre-run guidance and maintained property knowledge during execution planning.

For ongoing graph discovery and property management, review the property workspace alongside your workflow automation and run history.