Support Extensions/plugins to expand functionality

[mrud]

I am currently looking at librechat and really like the core of the offering but am currently interested in extending / customizing some aspects, e.g. seeding memory based on oidc claims etc.

Instead of just putting the functionality directly in the code I was thinking of potentially using extensions/plugins to allow extending functionality without having to modify directly core components.

Overall Design:

1. Introduce a hook registry, e.g:

  const handlers = new Map();

  function on(event, handler) {
    const list = handlers.get(event) ?? [];
    list.push(handler);
    handlers.set(event, list);
  }

  async function run(event, payload) {
    const list = handlers.get(event) ?? [];
    for (const handler of list) {
      try {
        await handler(payload);
      } catch (err) {
        // log, do not fail login
      }
    }
  }

  module.exports = {
    on,
    run,
    events: {
      IDENTITY_UPSERTED: 'auth.identity.upserted',
    },
  };

2. Define interface for extensions, initially very simple, e.g. extension exports something like:

  module.exports = function register(app) {
    app.authHooks.on('auth.identity.upserted', async (event) => {
      // extension logic
    });
  };

Is there interest to have a system like this? I would be happy to help drive/implement at least something like this if it aligns with the overall direction/vision of the project.

[likeabas]

Hi @danny-avila we ran into the same problem and right now customize a lot by swapping imports to local extension files.

Would you be open to a small PR for an optional module override layer (Vite + API resolve: if extensions/<same-path> exists, use it; otherwise stock LibreChat)?
No caller changes in core, no behavior change without overrides. Worth pursuing, or would you rather wait for a fuller plugin/hook API?