Skip to content

Make Services a top level entity and make Agents compose services and vaults #334

Description

@wjarka

I would like to suggest a design / architecture change.

Let's say I want to have two vaults - one using my personal Claude Code subscription and one using my work Claude subscription. And then two separate agents for this.

RIght now, I need to create two vaults, define the same services in both and then add credentials in both.

I believe Services should be defined once at the top level in the app - because a service is basically a rule / template for credential injection.

Vaults for storing credentials.

Agents compose the two.

So basically creating an agent would be:

  • add all service definitions the agent needs
  • add all vaults that have credentials needed for those services

That would allow for defining service definitions once and storing most credentials only once.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions