AI & ML interests

Applied AI. Agent infrastructure, local inference, and policy gates you can actually run.

Recent Activity

dipankarsarkar  updated a collection 13 days ago
Safe agent infrastructure
dipankarsarkar  published a Space 13 days ago
neullabs/agent-infra
dipankarsarkar  updated a Space 14 days ago
neullabs/agent-infra
View all activity

dipankarsarkar 
updated a Space 15 days ago
dipankarsarkar 
published a Space 15 days ago
dipankarsarkar 
posted an update 15 days ago
view post
Post
141
Your issue tracker is in the wrong place.

It lives on a server. Your code lives in git. So every time an agent picks up work it makes an API call, burns a token, fights a rate limit, and still cannot see what the other agent just did.

Move the issues into the repo. Append-only event log in git refs. Branches when you branch, merges when you merge, CRDT so two agents never conflict. No server, no database.

The coordination signal that PR-level telemetry misses lives before the pull request. The paper, and a live demo running the real tool:

Before the Pull Request: Mining Multi-Agent Coordination (2606.19616)
https://huggingface.co/spaces/neullabs/grite

If your agents share a repo, where does their shared state actually live right now?
  • 2 replies
·