Open datasets, benchmarks, and browser tools for inspecting, replaying, evaluating, and securing AI-agent trajectories.
Justin
solsticestudioai
AI & ML interests
Founder, Solstice AI Studio — synthetic datasets for BI, analytics, AI agent training, and embodied/robotics research. 100% synthetic, schema-custom, production-scale. solsticestudio.ai
Recent Activity
repliedto dipankarsarkar's post 1 day ago
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:
https://huggingface.co/papers/2606.19616
https://huggingface.co/spaces/neullabs/grite
If your agents share a repo, where does their shared state actually live right now? repliedto dipankarsarkar's post 1 day ago
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:
https://huggingface.co/papers/2606.19616
https://huggingface.co/spaces/neullabs/grite
If your agents share a repo, where does their shared state actually live right now? repliedto dipankarsarkar's post 3 days ago
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:
https://huggingface.co/papers/2606.19616
https://huggingface.co/spaces/neullabs/grite
If your agents share a repo, where does their shared state actually live right now?Organizations
None yet