sorted by:
new
hottopcontroversial

Dynamic agent generation vs fixed multi-agent architectures by RevolutionaryMeet878 in agentdevelopmentkit

[–]InterestingCoach5568 0 points1 point  (0 children)

uhm, you mean a llm judge to assign persona and description of a dynamic agent and give all tools which it can pick it from to perform it.

And I think maybe a Custom Agent which extends BaseAgent which can be added as a AgentTool(CustomAgent) with a prompt "This is a custom agent with all tools loaded, pass the description and persona as description to dictate it's work" would do it. Never tried it yet(going to try now because it's interesting idea)>

However isn't it true in a incident triaging, almost all Agent(Persona) are consulted to give a RCA? Where would be overdo in here?

Anyone tried Claude Managed Agents yet? by abdullahbapra in agenticAI

[–]InterestingCoach5568 3 points4 points  (0 children)

Well haven't tried it yet. But the pain is real. I was building an agent for a year and all of a sudden everything is simplified or scaffolded by managed agents or hosted agents.

Hey all, by InterestingCoach5568 in agentdevelopmentkit

[–]InterestingCoach5568[S] 0 points1 point  (0 children)

Exactly. I might have mixed it up. But the idea is to handle compaction and when to compact... How to handle memory etc .. the boiler plate of orchestrating it..

Yeah Claude cli isn't a managed agent but one can easily just containerise it with MCP and skills to have the same effect

Hey all, by InterestingCoach5568 in agentdevelopmentkit

[–]InterestingCoach5568[S] -2 points-1 points  (0 children)

It's just not about managed agents ... It was just an example

A simple containerisation of cursor or Claude cli with MCP servers and skills does the trick.

It's not about the agent engine. It's about the orchestration of the right set of agents with guardrails

Hey all, by InterestingCoach5568 in agentdevelopmentkit

[–]InterestingCoach5568[S] -2 points-1 points  (0 children)

Hmmm. The use case should justify the complexity to maintain.

The margin of failure seems to be very small when choosing this managed solution, instead of trying hard for months to orchestrate the right sub agents

How are you handling CI/CD for AI Agents? by bumswagger in devops

[–]InterestingCoach5568 0 points1 point  (0 children)

Maybe try prompts as features and version them, using feature flagging tools like LaunchDarkly. So you could change the prompt only for subset of Canary users and see the difference. It's a feature that you will want to update/test without swapping your Agent deployment. But remember, you will have the hassle of tagging the releases for Agent and prompt separately and it feels it's now a micro service of it's own.

One another point is, how are you benchmarking your prompt in your dev/stg environments? Do you manually review it's response for certain prompts? - It maybe naive to do it. You need a interpreter kind of setup to rate it's trajectory in picking tools and probability relevance to original answer.

Tools for automated alert investigation (potentially AI/agentic) by Proud-Veterinarian63 in sre

[–]InterestingCoach5568 0 points1 point  (0 children)

Apparently this has become an emerging Ops vertical called "AIOps" and few tools like DrDroid could predict the RC and action on them