Repository navigation
Description
Use case
We use self-hosted Executor with Hermes and multiple users. We want to maintain one shared Outlook app, while each person can ask their agent to add personal tools, skills, workflows, schedules and webhooks to it.
For example, one person wants a mail-review workflow and briefing instructions, while another wants different mail handling. Each should use their own Microsoft account and schedule. They should not need a separate copy of the entire Outlook app, and their changes should not alter the shared definitions for everyone else.
In our current v2 setup, tool, skill, workflow, schedule and webhook definitions live in app source. A member can use a shared app, but adding these definitions means editing shared source or making a personal app copy. Personal account links and schedule instances do not provide personal definitions alongside the shared app.
Observed on self-hosted Executor 2.0.0-beta.43 with an authored test app using apps@0.0.1-beta.126.
Requested behavior
Support personal tools, skills, workflows, schedules and webhooks attached to an existing shared app, alongside its shared definitions:
- Organization-managed definitions remain shared and centrally maintained.
- A regular member can create, inspect, update and remove their own tools, skills, workflows, schedule definitions and webhook definitions without gaining permission to edit the shared app or another user's additions.
- Agents discover the shared definitions plus the signed-in person's private additions. Other users do not see or invoke those private additions.
- Personal tools and workflows run with their owner's own linked accounts and permissions. Ownership comes from authenticated Executor identity, not a user ID supplied in tool input.
- Support user-created schedule definitions, not only personal instances of schedules declared in shared source. Keep existing per-user instance behavior, and allow a person's schedule to invoke their personal tool or workflow. Users manage their own timing, timezone and enabled state; publishing a definition should not automatically enable it for anyone.
- Support personal webhook definitions and registrations, with registration, verified event delivery and teardown bound to the owning user/account. One user's webhook must not invoke another user's private tools or workflows or receive their events. Defining or sharing a webhook must not silently register it for everyone.
- Shared app updates preserve personal additions. Define name-conflict behavior explicitly so a personal addition cannot silently replace a shared one.
- Personal additions cannot broaden organization access or bypass mandatory shared policies. Any supporting private state must remain isolated between users.
The desired agent flow is: “Add a personal mail-review tool, skill and workflow to my Outlook app, with my own schedule or webhook trigger.” The result should be attached to that shared app for that user, rather than a new integration copy or a shared-source edit. It should be manageable through native authoring tools.
Acceptance example
Alice and Bob use the same shared Outlook app with separate Microsoft accounts. Alice adds a private tool, skill and workflow, plus her own schedule and webhook trigger. Her agent discovers and runs her additions against her account; Bob's agent cannot discover or run them or manage her triggers. Alice's schedule and verified webhook events invoke only her workflow under her account. Bob can add his own definitions, and updating the shared Outlook app preserves both users' additions, trigger settings and account isolation.
Related work
- Expose caller identity to app code #2346 and Support per-user app data with authenticated caller identity #2440 address authenticated caller identity and per-user app data. Those look like useful foundations, but do not provide this personal-definition authoring model.
- Reusable organization and group policies for automatic scoped connection provisioning #2551 covers reusable scoped-connection provisioning, which is a separate onboarding need.
- Add managed Agent Skills #2091 proposed personal/workspace-owned managed skills and was closed without merging. Some of that ownership model may be relevant, alongside native workflows.
I searched the open and closed issues and PRs and did not find an exact request for personal definitions alongside the shared app.
Activity
[-]Support personal skills and workflows alongside shared app definitions[/-][+]Support personal tools, skills, workflows, schedules and webhooks in shared apps[/+]