Hacker News Reader

Comment by zwigglers | Hacker News Reader

It sounds like you're describing two chat sessions = two agents, one chat session per agent. The agents get different tools, no shared context, no duct tape. Is this an accurate read?

The duct taping comes in when two different people share an agent, when having a shared context is useful.

The shared context use case is less common. You have to have hit that wall yourself to feel the problem. Does that track?

View on HN

Yes, since you said that you're two people, then what you begin with is exactly that, right? The session sharing is something you've layered on top, with extra software, not something you basically get from a VPS+UNIX users, right?

The times I've shared contexts in such ways, then you want to share a read-only view, still with the other user not being able to add more messages, I guess you're really talking about group chats here?

> The session sharing is something you've layered on top, with extra software

Nope. If you give access to the same agent instance to multiple people, then one user can get access to someone else's data. I'm working right now for a startup facing this issue. The easiest solution is to have a separate agent instance per user, but this increases resource consumption vs having a single agent instance with proper separation between multiple users.

If you're trying to solve this problem right now you should take a look at cast and see if it addresses your problem. Would love to stress test my framework against different use cases.

Reply on news.ycombinator.com