DocsBook a demo

Platform

Platform overviewArchitectureWorkflow orchestrationGitOps configurationGovernance and AAAAI and MCPKnowledge and contextRuntime and executionEvidence and monitoring

Use cases

All use casesProduction incidentRelease preparationHotfix to productionSecurity scan triage
Why NopsAIIntegrationsSecurity

Resources

All resourcesAI agent governanceMCP governanceMCP securitySelf-hosted platforms
PricingGitHub

Company

How a run worksAboutContactBook a demo

Assistant chat

In-product chat with page context, and exactly what that context contains.

ConceptOperatorAutomation authorSecurity

Key points

  • Current-page context is metadata only: route, page area, active tab, team and scope, selected resource IDs, and allow-listed filters.
  • The composer renders a removable context chip so you can see and drop the context before sending.
  • The Assistant does not scrape page text, logs, secrets, credentials, or arbitrary query parameters.
  • Assistant selects from the same models pipelines use, filtered by what the caller may access.
  • Conversations are per-user and can be deleted; memory can be compacted with a summarize action.
  • Assistant availability and individual features are configuration-controlled.

How it works

AI Evaluation on analysis surfaces is a separate mechanism. It uses the analysis evaluation endpoint rather than creating an Assistant conversation, and it does not ask hosted MCP to inspect resources.

If Assistant reports that no model is available, configure provider, model, credential reference, and scope access in Models — the same place pipeline goals get their profiles.

Examples

See what the assistant is allowed to do for this callerbash
# feature families enabled for the install
curl -s -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/assistant/config" | jq

# models the caller may drive the assistant with
curl -s -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/assistant/models" | jq

# conversations belong to the caller
curl -s -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/assistant/conversations" | jq
Result

Configuration decides which capability families exist; AAA still decides the specific resources and actions the caller may reach through them.

Implementation evidence

  • doc/assistant-capabilities.md

    User-facing capabilities and example prompts per feature area.

  • services/ui/src/features/assistant/pageContext.ts

    Exactly which page metadata is collected.