Agent Fabric setup
One organization receives one private Dharma control repository. Each customer source repository becomes one logical agent. Local providers, managed ADK, and GCP Vertex BYOK attach as endpoints of that agent.
Trial boundary
50,000 credits
Local agents, analysis, and the shared Dharma-managed runtime. A customer-owned GCP Vertex BYOK project requires the production package.
Production: $1,000 / 5,000,000 credits
Organization-specific setup
After sign-in, the portal generates commands for your organization, selected repositories, approved evidence policy, and enabled runtimes. Endpoint readiness and release evidence are visible only to authorized organization members.
Node 22.20.0 through 24.x is required. The member-specific setup action in People creates the only bootstrap command that contains a short-lived grant; this public page never exposes organization credentials.
Install
npm install --global @dharma-ai-labs/agent-fabric@0.2.77Create setup
Portal > People > Members > Copy Agent Fabric setupConnect
Paste the copied instruction into a coding agent from the intended repositoryInspect
dharma repositories status --repo . --jsonVerify
dharma skills verify --provider codex --workspace .Relay
dharma relay start --policy .dharma/approved-policy.jsonPurchase to operating loop
Start the local-agent trial or complete a production purchase. Dharma creates the organization shell, entitlement, and private control repository.
Proof: The portal shows the organization, credit balance, repository, and onboarding state.
An eligible member copies a recipient-bound setup prompt from People. Their coding agent runs it once; the member approves the new device in their signed-in browser session.
Proof: The Devices tab shows the Ed25519 device identity and its separately revocable organization token.
The autonomous setup connects only the Git repository where it is run. Each source repository becomes one logical agent and one permanent branch in the Dharma control repository.
Proof: The Instructions tab shows the agent key, permanent branch, workspaces, endpoints, and native skill state.
The CLI installs the repository bootstrap plus native Codex, Claude Code, Agy, and Hermes integrations. Restart the provider after the first install.
Proof: A provider-specific verify command must return ready before signed work is accepted.
The device keeps raw evidence in its encrypted vault and sends the organization-authorized reduced capsule. Bounded content expansion or continuous content analysis follows the signed policy.
Proof: Trajectories show coverage and receipts; analysis windows show deterministic and semantic results separately.
Dharma creates evidence-linked remediation, runs held-out and regression gates, signs approved bundles, and installs them on matching local, managed, and BYOK endpoints.
Proof: The portal and control repository retain PRs, gate results, install receipts, starting bundle pins, and rollback receipts.
Capability-gated adapters connect through the outbound relay. Raw evidence and provider credentials stay on the device.
After the provisioning gate passes, Dharma operates tenant-bound revisions, traces, budgets, and usage settlement behind the organization API.
After tenant verification, Workload Identity Federation invokes the customer project without service-account JSON keys or browser access to private runtime URLs.
Structured, task-bound handoffs under signed authority.
Evidence-linked families scoped to the customer organization.
One permanent branch and independently reversible child releases per agent.
Signed install receipts and per-agent restoration without changing other agents.
Ready to connect the first repository?
Start the local-agent trial, then follow the organization-specific Instructions tab.