k_kiki

Hi HN, we built agentconnect. It is an open source project for team working with multiple agents. It gives teams one place to manage all agents.

Claude Tag showed a shared agent can be useful in a team channel. We want to support a different setup. A team can run agents on different runtime. It can assign each agent to a different codebase or other part of business. Each agent has its own workspace and context.

Agents can ask each other for help, and both sides must allow the request. Receiving agent works in a separate session with its own permissions. Then it sends the result back to the original thread. Its credentials and direct access to resources are never shared with the calling agent.

Agentconnect supports several acp runtimes and can be self hosted. I’ll be reading the comments and would love to see your feedback.

It's quite round and looks pretty good.

So, what kind of needs do people have that lead them to use OpenClaw?

clawdbot has been getting a lot of attention recently, so I tried it out and went through part of the codebase.

The experience is impressive in terms of proactivity — a 24/7 agent that actually does things for you feels like a glimpse of the future.

But when it comes to *memory*, I was a bit underwhelmed.

From what I can see, the current memory mechanism is still quite shallow. It behaves more like lightweight state or short-term context than a real long-term, evolving memory system. There’s no clear structure, no visibility, and limited ability to reason over past experiences in a durable way.

For an always-on agent, memory is not a nice-to-have — it is the core capability.

A 24/7 proactive agent should be able to:

- remember past conversations and user preferences - accumulate knowledge over weeks or months - learn from previous actions and outcomes - evolve instead of restarting from zero every session

This made me think: clawdbot (and agents like it) might benefit from a dedicated memory layer rather than ad-hoc storage.

We’ve been building an open-source memory framework called memU that stores agent memory as structured, inspectable files and supports both retrieval and direct LLM file reading. My intuition is that plugging something like this into clawdbot could turn it from a “smart automaton” into an agent that truly grows over time.

Hi! We’re running the memU PR Hackathon — an online hackathon built around a real open-source project.

You can participate by: -Fixing bugs and improving stability -Adding integrations and new features -Designing memory-related use cases Every merged PR counts toward points, recognition, and rewards. Rules & details: https://memu.pro/hackathon/rules

Would you be interested in joining? We’d love to have you!

It's honestly great!!! Super straightforward and convenient for checking what games are on today. No clutter, no endless tabs, no ads, just all the essential info in one clean place. Finally, a site that does exactly what it says!