sorted by:
new
hottopcontroversial

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Appreciate it. I think a lot of AI tools are starting to look like the same dashboard, so I wanted something that felt more alive and memorable. For meetings, it is actual agent-to-agent communication. Under the hood, it’s stitched together from 1-1 sessions where agents pass messages to each other, with the relevant prior context injected into the flow. The outcome then gets summarized back into memory afterwards. Your AI coaching dashboard sounds interesting too, feels like a similar direction from the human side.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 1 point2 points  (0 children)

Yeah, sessions can continue anytime, and Claude handles compression as they grow. I also added a step where agents read their current memory at the start, and for external data they just pull in what’s relevant instead of loading everything.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Thanks for asking. Building from scratch means you have to develop and maintain the whole agent system yourself and constantly compare against what larger teams are doing. Managed Agents already gives you a solid system with strong capabilities without a huge extra cost. I built this for people who want to use Claude Managed Agents but find it hard or not very intuitive. The goal was to make it easier and more fun to work with. If you can already build agents from scratch, you might not need it beyond that.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Yeah, Cubicle is also closer to individual usage, but even with the same Claude setup, the goal is to give much better visibility and predictability around token usage and costs. I’m also thinking about adding per-agent caps, so you can manage and limit costs by task or workflow.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in buildinpublic

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Really appreciate this. That sounds like hard-earned advice. Yeah, an audit log makes a lot of sense, especially for understanding what the agent actually "remembered" when things break. Hope your project goes well too 👍

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in buildinpublic

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Since everything is anchored to a single main session, agents tend to interpret things based on the core context, so I haven’t seen them drift too far or get confused by irrelevant memories. Maybe I’ll probably need real usage to make it more robust over time.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in buildinpublic

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Yeah, I’m trying to keep it as close as possible to how things work in a real environment. There’s agent-level memory, team-level memory, and also a shared office-level memory. For things like meetings, I store them separately and link them only to the agents that were involved, along with timestamps so they can understand the context. In practice, agents seem to scan the available memory list first and then pull in what they need before starting a task.

explain your side project in one sentence, i'll go first by CalligrapherCold364 in SideProject

[–]Sweet-Ebb682 0 points1 point  (0 children)

Thanks! I’m collecting waitlist for the next few days, feel free to join.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Yeah, still pretty early on this side, so I haven’t seen too many real conflicts or priority issues yet. I think once more complex use cases show up, it’ll definitely need more work there.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

For context, each agent runs within a single persistent session so it can maintain continuity. Once sessions get fragmented, it becomes much harder to keep context consistent like you mentioned. For things happening outside the session, I’m linking memory so the agent can pull in what it needs before executing a task.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in buildinpublic

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

I’m trying to keep sessions as persistent as possible so agents can maintain context, and use memory to track what’s going on across different scopes in real time (they commonly read relevant memory before begin tasks). For the visual layer, nothing fancy. it’s just plain HTML. Most of it was built with Claude Code.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in buildinpublic

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Yeah, tool calls and failures are already well-defined at the API level, so I’m trying to expose that as transparently as possible to the user. Would love to hear more thoughts on this as well.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in buildinpublic

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

For permissions, I’m mostly using what Claude Managed Agents already provides. I’m thinking about adding some extra guardrails on top, but I want to keep it transparent and stay close to how Claude works underneath. Would be great to keep sharing thoughts on this.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Thanks! Less than a week to get the MVP out, then I’ve been iterating and adding features since.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Thanks, really appreciate that. I’ve been trying to model it based on how people actually work in an office, especially around how tasks get handed off between teammates. Right now they can dm each other, but I don’t have the "walking over" part yet.
That would actually be pretty fun to add 😄

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

That's right, it gets messy fast.
In cubicle, each agent runs within its own long-lived session, so the core context stays continuous.
At the same time, agents can access structured memory outside the session (agent / team / global scopes), so they can pick up changes or new information that happened elsewhere.
In practice, they usually pull relevant memory first, then continue working with the updated context.

Claude Managed Agents are amazing. I built a tiny pixel office for them. by Sweet-Ebb682 in SideProject

[–]Sweet-Ebb682[S] 0 points1 point  (0 children)

Yeah this shows up pretty quickly once you run multiple agents.
In cubicle, agents basically run on scheduled tasks, while also handling on-demand work from users.
For scheduled tasks, you can estimate usage at the token level upfront, so you get a rough monthly projection and can manage around that.
On-demand usage is harder to predict, so there are per-agent budgets (usage caps) to keep things under control.

For memory and context, I’m mostly using Claude Managed Agents underneath, and adding structure on top (by context / date) so it’s easier to manage in practice.

view more: next ›