Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to providers concept #257

Open
tomkis opened this issue Mar 4, 2025 · 0 comments
Open

Improvements to providers concept #257

tomkis opened this issue Mar 4, 2025 · 0 comments

Comments

@tomkis
Copy link
Collaborator

tomkis commented Mar 4, 2025

Let's use this ticket as a

Current limitations of Providers concept

  • Env variables cannot be scoped to agents, there is now way how I can have 1 provider with 2 agents, each using different models)
  • Provider is tightly coupled with agent - agent's dependencies and installed and run with provider, providers are not lightweight as intended
  • Agent installation is happening magically under the hood - it should happen at users request (agent installation might fail, essentially fails all other agents within the provider; like with ollama, user should be able to see the installation and it's progress)
  • Model and other dependencies should be installed only when user needs the agent - for example if agent depends on llama 3.3 from ollama, I only want this dependencies to be installed on user request
  • deployments - we need to be able to deploy agents as standalone docker containers, not a group of agents within provider; also, I think the manifest should follow k8s manifests (envs, configmaps, secrets)

Resource Utilization

Runtime Configuration

Security

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant