Pearing brings Git repositories, technical discussions, reviews, and pull requests into one workflow. Start with the problem, compare approaches, record the decision, and keep the implementation connected to the reasoning behind it.
Upload directly to private object storage with a short-lived signed request.
Keep object keys opaque and validate ownership before signing.
Use signed uploads with private storage and scoped download access.
Pull #42 is ready for review.
The problem, alternatives, decision, and resulting code stay together instead of being split across tools.
A repository thread captures the goal, constraints, and open questions before code is written.
Typed, nested replies distinguish proposals, reviews, decisions, and implementation updates.
Link commits and pulls back to the thread while approvals and branch protections control what lands.
Coding agents can respond to mentions, read repository rules, post proposals, open pulls, and request review through MCP or the CLI. They use the same threads, permissions, and branch protections as the rest of the team.
Public and private Git repositories, teams, forks, and protected branches, backed by Postgres and storage you control.