> ## Documentation Index
> Fetch the complete documentation index at: https://docs.riktra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Follow changes with your AI

> Let a compatible AI client know when company context or skills have changed.

A long-running AI conversation can keep using information it fetched earlier.
Riktra can send a small change signal so a compatible client knows to fetch
current information again.

This is an **experimental integration** using the draft MCP Events contract.
It requires a client that supports that contract; connecting Riktra alone does
not make every AI conversation receive signals.

## Ask your client to follow changes

In a compatible client, connect Riktra and refresh its event catalog. For example,
ChatGPT's MCP Events integration supports user-requested monitoring in eligible
Work and dot experiences. Availability also depends on your workspace settings.
See [the client's setup instructions](https://developers.openai.com/plugins/build/mcp-events).

Then explicitly ask for the behavior you want:

> Follow changes to my company's direction and decisions in Riktra. When they
> change, fetch current company context again and tell me what matters for my work.

You can also ask it to follow changes to the organization's published skills.
The signal itself contains revision metadata, not company records or personal
context. The client still reads current information through the same permissions
as your regular Riktra connection.

## Stop monitoring

Ask the client to stop its subscription, or open **Settings → AI change signals**
in Riktra and stop your subscription there. You see only your own subscriptions.
A delivery that was already in flight may still arrive after you stop it.

Subscriptions expire after at most 24 hours unless the client renews them. They
also stop receiving signals when you lose access to the organization. Several
changes can be combined into one signal, and delivery may be delayed or fail.
A delivered signal does not prove that the client fetched or used new context.

Change signals never approve proposals or change shared company truth. Your
client's requested response and Riktra's existing approval process remain separate.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.