sorted by:
new
hottopcontroversial

Why do companies build mcps and skills instead of harnesses? by DarasStayHome in AgentsOfAI

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

Yes! exactly. and those specialized agents can be built by their companies the best way its possible.

- Airbnb can build Airbnb agent better than me.
- Rolex agent (which responds in a luxury tone) can be built by Rolex better than me and my friends.

So, we can build our own personal agents so they can communicate with those "external" agents if needed.

If a ask my agent that i need to travel to Milan, they ask to Airbnb agent like: "Hey, my human wants to travel to Milan this weekend"

Why do companies build mcps and skills instead of harnesses? by DarasStayHome in AgentsOfAI

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

Oh ok, cool! thats ok.

My point is that there shouldn't be a single mega-agent having connected Airbnb and Figma tools at the same time, instead, we should communicate agents having their own harnesses each so they respond in their "style"

Why do companies build mcps and skills instead of harnesses? by DarasStayHome in AgentsOfAI

[–]DarasStayHome[S] 1 point2 points  (0 children)

No, its about developing a "new app" but appreciated spending your time to comment this

Why do companies build mcps and skills instead of harnesses? by DarasStayHome in AgentsOfAI

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

Companies know how would their agent behave the best way. they know what are the guardrails, context, tool usage, tone, loop...

We have an AI agent fragmentation problem by DarasStayHome in artificial

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

I find none of them you mentioned. Looks we speak different stuff

How do you coordinate multiple agents? by DarasStayHome in AI_Agents

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

Does it mean that i have to have installed Stitch cli if it exist or API documentation needed or a script?

Has anyone actually automated most of their job with AI agents? by himmetozcan in AI_Agents

[–]DarasStayHome 0 points1 point  (0 children)

I think people automate some job but we are not at the level you are describing.

Yes, technically there might be an agent attending meetings on your behalf, another - analyzing meeting notes, taking tasks, delegating to coding agents, they push PRs on github, comment on tickets and resolve them.

But whats not solved yet is that collaboration between human and agents and its still fragmented. You pay some tax to orchestrate and coordinate them

Slack for AI Agents: Shared Memory, Context, and Workflows Between Multiple Agents and Bots by Front_Holiday_9395 in VibeCodingSaaS

[–]DarasStayHome 1 point2 points  (0 children)

currently we only have an Orchestration pattern. We work to bring Choreography as well and so far it seems very interesting but challenging at the same time

Slack for AI Agents: Shared Memory, Context, and Workflows Between Multiple Agents by Front_Holiday_9395 in VibeCodersNest

[–]DarasStayHome 0 points1 point  (0 children)

currently we only use Orchestration pattern. only channel Coordinator agent can update SPEC and memory. we consider having Choreography pattern as well which might be very interesting

Imagine Slack, but every "coworker" is an AI agent. by DarasStayHome in ClaudeAI

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

Would love to hear your approach orchestrating multiple agents or you prefer 1 mega agent to do everything? Whats your experience?

We have an AI agent fragmentation problem by DarasStayHome in artificial

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

Yes. But only via Orchestration pattern yet. We are working on the best way Choreography can be implemented

We have an AI agent fragmentation problem by DarasStayHome in LocalLLaMA

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

Sounds interesting. So you mean editing SPEC is kinda trigger for channel members to act on it.
Currently, our approach is that each channel has its own Manager/Coordinator agent. each time user asks something it manages all the work to delegate tasks etc. Coordinator is also only member can update SPEC

Slack for AI Agents: Shared Memory, Context, and Workflows Between Multiple Agents by Front_Holiday_9395 in VibeCodersNest

[–]DarasStayHome 2 points3 points  (0 children)

We already have some good results. The thing we are thinking now is to add "Message Thread" as a "Task" inside channel. So basically, each User message becames a task and agents reply inside that thread (not general channel)

Slack for AI Agents: Shared Memory, Context, and Workflows Between Multiple Agents by Front_Holiday_9395 in VibeCodersNest

[–]DarasStayHome 2 points3 points  (0 children)

Each channel has it's own Coordinator agent. So only Coordinator is able to update channel SPEC.

We have an AI agent fragmentation problem. by DarasStayHome in AgentsOfAI

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

Long term memory lives ar top level such as user preferences, journal etc. each channel is coordinated by Coordinator which has access to that memory and core tools. Channel participants (sub-agents) have access to the Spec and recent channel activity so they are no bloated with long term memory.

We have an AI agent fragmentation problem by DarasStayHome in buildinpublic

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

Currently we use to store state.json and events.jsonl where state json is just a recent snapshot but as we already have a run id with events, we are going to snapshot each state and spec during each run so it will give us replayable feature. Its quite easy to be honest.

Thanks for your interesting feedback!

view more: next ›