Lookout Context Hub Private Beta

Understand how Lookout uses the Context Hub to store documentation, team notes, agent memory, and reusable skills.

The Context Hub is your workspace’s knowledge store. It holds what your team and the agent have learned, so the agent can pull it into later conversations for grounded answers and your team can find what was figured out earlier.

In the workspace sidebar, the Context Hub appears under Context.

The Context Hub showing generated docs, notes, and memories

What it holds

The Context Hub combines three kinds of items, all searchable together:

  • Generated documentation: AI-generated descriptions of how your sources and events are instrumented
  • Team notes: Knowledge your team shares manually
  • Memories: Facts the agent captures from conversations so it can remember them later

The Context Hub page has a keyword search box for finding an item by name or text. When the agent searches the hub during a conversation, it uses a richer hybrid search that combines keyword and meaning-based matching.

Generated instrumentation documentation

To understand what a codebase actually tracks, Lookout generates a structured document describing the RudderStack events and properties it finds in a linked repository. It clones the repository into an isolated sandbox, scans for analytics calls, and produces a document that lives in the Context Hub alongside your notes and the agent’s memories.

This documentation is generated from your source control, not from chat. It is produced when:

  • You select Generate Context or regenerate an existing document in the Context Hub.
  • A push lands on the default branch of a linked GitHub repository that has documentation enabled. Lookout refreshes the affected docs automatically.
info

Automatic push-triggered refresh applies to GitHub only.

For GitLab-linked sources, regenerate the documentation manually from the Context Hub. In chat, the agent can read these generated docs to ground its answers, but it doesn’t generate them.

Notes and memory

  • Notes are written by your team and are a good place to capture conventions, definitions, and context you want the agent to use.
  • Memories are captured by the agent during conversations. You control whether the agent captures memory with the memory capture setting, and captured memories appear in the Context Hub where you can review them.

Skills (slash commands)

A team note can be promoted to a skill — a reusable instruction set the agent follows for a particular task. To use one, type / in the chat composer and pick the skill; its instructions are added to your prompt before the agent runs.

info
Skills are a good way to standardize a repeated task — a recurring analysis, a documentation format, or a review checklist — so anyone on the team gets a consistent result.

Admin controls

A workspace Admin can control what knowledge the agent can use and save, from the controls at the top of the Context Hub, for example, whether the agent draws on team notes and memories, whether it uses generated context, and whether it captures new memories from chat.

All members can see these controls. However, only admins can change them.

See Chat and Ask Questions for more details on how the agent draws on this context during a conversation.


Questions? We're here to help.

Join the RudderStack Slack community or email us for support