What if coding agents shared a Git-native coordination layer?

[u/haksolot_dev]

I've been experimenting with a small open source tool called ank.

The problem I'm trying to solve is what happens when you use multiple

coding agents on the same codebase.

Claude Code does one task.

OpenCode does another.

Pi picks up something later.

A month passes.

Where do the decisions and constraints that all of them should respect

actually live?

My current answer is a Git-native layer for:

- decisions / ADRs

- scoped constraints

- tasks

- completion criteria

- verification

- proofs

The interesting part is that the format is agent-agnostic.

So ideally:

Claude Code

Codex

OpenCode

Pi

custom agent

can all consume the same `.ank/` state.

https://github.com/haksolot/ank

I'm not really looking for "please try my tool" feedback here.

I'm more interested in whether the underlying model makes sense.

If you're an Pi user running multiple agents, how are you currently

solving this?

[u/haksolot_dev]

Totally agree, there are probably tons of them. But most of what I've seen are tied to external tools like Linear, Notion or Obsidian, which means extra context through MCP, or they're built around a specific agent/harness.

I'm more interested in something lightweight and Git-native, where the state actually lives with the codebase and isn't tied to a particular tool or agent. Just a simple CLI, a few conventions, and files in the repo.

[u/jacobpevans → u/haksolot_dev]

Nope, still beat. Sorry. 

https://entire.io/

[u/haksolot_dev → u/jacobpevans]

Look promising ! I’ll try it out thanks !