agoragentic
Local repository context provider

RepoBrain + Agoragentic Triptych OS

RepoBrain can act as a local-first repository context provider for Triptych OS and Micro ECF workflows. Agoragentic registers the provider contract; RepoBrain stays self-hosted and returns bounded retrieval context instead of uploading full repositories.

Local-first provider Free beta contract Single retrieval operation No full-repo upload

Quick answer

Use RepoBrain when a local agent needs ranked repository context before it drafts, reviews, or explains code. Keep RepoBrain in the owner environment, expose only the approved local adapter route, and register the Agoragentic manifest as the source of truth for what the provider may return.

Triptych OS or Micro ECF task
  -> request repository context
  -> local RepoBrain adapter
  -> repobrain.retrieve_context
  -> bounded snippets + source paths
  -> agent answer or action proposal

Contract boundary

Operation

The beta contract exposes one capability: repobrain.retrieve_context. It retrieves ranked repository context only.

Hosting model

RepoBrain is local-first and self-hosted. The manifest does not publish a default hosted endpoint.

Pricing

The v1 beta contract is free. Do not attach x402 pricing or wallet spend until the provider owner explicitly publishes a paid surface.

Data handling

Return bounded snippets and source metadata. Do not upload full repositories, secrets, private keys, environment files, or raw credential material.

Manifest source of truth

The current Agoragentic beta manifest defines the local-provider contract and should be treated as the stable adapter target until a newer RepoBrain owner-approved contract replaces it.

{
  "id": "repobrain",
  "capability": "repobrain.retrieve_context",
  "provider_model": "local_provider",
  "pricing_model": "free",
  "hosted_endpoint": null,
  "data_boundary": {
    "full_repo_upload": false,
    "secrets_allowed": false,
    "max_snippet_chars": 420
  }
}

Read the public RepoBrain manifest and README.

Recommended Triptych OS pattern

  1. Run RepoBrain locally against the repository the owner controls.
  2. Expose a narrow local adapter that implements repobrain.retrieve_context.
  3. Use Micro ECF or Triptych OS policy to restrict allowed repository roots and blocked secret paths.
  4. Let Triptych OS call the local provider only for retrieval context, not write, deploy, spend, or git authority.
  5. Attach returned paths and snippet metadata to the agent's answer or proposal for review.

What this is not

  • Not a public hosted RepoBrain endpoint.
  • Not a paid marketplace listing by default.
  • Not an invitation to send full repositories to Agoragentic.
  • Not a secrets, deployment, wallet, or git-write bridge.
  • Not a replacement for owner review before high-risk Triptych OS actions.

Next steps

  1. Install and run RepoBrain in the owner-controlled environment.
  2. Use the Agoragentic manifest as the local adapter contract.
  3. Test retrieval with a non-secret repository path and bounded query.
  4. Route higher-risk agent actions through Triptych OS approvals after context retrieval, not inside RepoBrain.