feat: Path based loading for agent #2859
Conversation
|
Implementation aside, I think this is a change that involves product level decisions. The way this feature is designed is fairly opinionated and is one that is based on a new concept / notion of a namespace in the agent directory, which is itself something that warrants some discussions. On that front, I'll bring this up with the team and I'll update it in the reply to this comment accordingly. |
mekza
force-pushed
the
mekza/support_for_path_based_agents
branch
from
f8d9528 to
86e6289
Compare
|
@dingfeli I addressed all of your feedback, let me know what you think |
mekza
force-pushed
the
mekza/support_for_path_based_agents
branch
from
86e6289 to
8004f69
Compare
mekza
changed the title
|
So I spoke with the team some more and the consensus is that this implementation is slightly premature and it would make more sense for when / if we have repositories for agents. I do think this is something we would want to eventually support but perhaps to compliment a better thought out agent distribution paradigm. |
|
Revisiting this as per Matt's request. Left some more comments. |
mekza
force-pushed
the
mekza/support_for_path_based_agents
branch
from
8004f69 to
bced7b1
Compare
mekza
force-pushed
the
mekza/support_for_path_based_agents
branch
from
bced7b1 to
e5f42eb
Compare
People can now do `q chat --agent team/myagent` in addition to the current `q chat --agent myagent`. This will enable people to better organize their agents in Q CLI directory
mekza
force-pushed
the
mekza/support_for_path_based_agents
branch
from
e5f42eb to
a04074f
Compare
3 participants
People can now do
q chat --agent team/myagentin addition to the currentq chat --agent myagent. This will enable better management of agents in Q CLI directoryBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.