Triggers on agent component tables

[alifarooq9]

I tried to add support for triggers on agent component tables by following the convex-helpers Triggers docs. The setup works when I register triggers inside the agent component package itself, but it does not work when I expose triggers and register them in example apps.

I’d like help understanding why this discrepancy happens and how to fix it.

---

Steps Taken

1. Added triggers.ts with the following code:

import { mutation as rawMutation, internalMutation as rawInternalMutation } from "./_generated/server.js";
import type { DataModel } from "./_generated/dataModel.js";
import { Triggers } from "convex-helpers/server/triggers";
import { customCtx, customMutation } from "convex-helpers/server/customFunctions";

const triggers: Triggers<DataModel> = new Triggers<DataModel>();

export const mutation = customMutation(rawMutation, customCtx(triggers.wrapDB));
export const internalMutation = customMutation(
  rawInternalMutation,
  customCtx(triggers.wrapDB),
);

export { triggers };

2. Updated all mutations to use this new mutation wrapper.

---

Problem

• ✅ Triggers work fine when registered inside the agent component package.
• ❌ Triggers do not fire when I expose triggers and register them in example apps.

---

Question

What could be causing triggers to fail when registered outside the component package?

[alifarooq9]

Related to #148

[ianmacartney]

Yes this is expected - triggers wrap the DB object, and outside of a component you don't have access to the component's DB object - which is intentional / by design. Even if there were an exported triggers handle, it wouldn't be able to call your code directly from inside a component - they run in different contexts (one has a handle to the component's db, the other to your app's db).

I'd rather expose some explicit callback API at the appropriate time - can you say more about what you're trying to achieve?
e.g. are you wanting to do something every time a message is saved during generation?

[alifarooq9]

Yes I want to trigger a certain function when the agent component tables changes, for eg; summaries of message

Yes this is expected - triggers wrap the DB object, and outside of a component you don't have access to the component's DB object - which is intentional / by design. Even if there were an exported triggers handle, it wouldn't be able to call your code directly from inside a component - they run in different contexts (one has a handle to the component's db, the other to your app's db).

I'd rather expose some explicit callback API at the appropriate time - can you say more about what you're trying to achieve?
e.g. are you wanting to do something every time a message is saved during generation?