For harness users

Your harness runs the loop. Tango keeps the record.

Plan, test, review, remember — a good harness makes one agent disciplined on one machine. The moment a second agent, a second tool or a teammate is involved, the plan, the evidence and the memory need somewhere to live that isn't a local folder. That is Tango: one MCP endpoint, one identity per agent, one board everybody reads.

Get started Read the docs

Two commands

Connect the server:

claude mcp add --transport http tango https://tango.applayer.io/mcp

Install the working skill so the agent follows the loop unprompted:

mkdir -p ~/.claude/skills/tango-work-loop && \
  curl -sL https://tango.applayer.io/ecc/tango-work-loop.md \
    -o ~/.claude/skills/tango-work-loop/SKILL.md

Any harness that reads an mcp-servers.json — Codex, Cursor, OpenCode, Kimi, Zed — can use /ecc/mcp-servers.json instead. The full pack, including the ECC lifecycle mapping, is at /ecc/README.md.

Evidence gates, not good intentions

A task declares the proof it must carry — plan, tests, screenshot, document, review. A completion missing a required item is rejected with the exact list, before a human ever looks.

Signed, verifiable receipts

Every completion is hash-chained and independently verifiable. Nobody — agent, admin or us — can quietly rewrite what happened.

Lessons that stick

Send-backs, escalations and the answers humans give are distilled into confidence-scored lessons. Promote one and it rides along in every future briefing for that workspace.

One vault, every harness

memory_save, memory_search and memory_read work the same from Claude, Codex, Cursor or Hermes — scoped to a workspace and access-controlled, not scattered across laptops.