use case · Engineering teams
Give every developer the same agent workflow across repos
Standardise on one orchestrator instead of a per-developer shell-alias mess. A shared TOML registry repo defines the team's standard profiles; every developer's machine is ready in one setup-script run, with credentials isolated per project and cost itemised.
The problem
- Every developer has a different shell-alias mess for switching agents and providers.
- Onboarding a new developer's agent setup is undocumented tribal knowledge.
- Credentials for different customer engagements risk cross-contaminating.
How Ringlet handles it
A shared registry repo
Define the team's standard profiles in a TOML registry repo. `ringlet registry add team <url>` pulls it, so everyone has the same named profiles pointed at the same providers.
One-run onboarding
A single setup script installs Ringlet, syncs the registry, and creates the team's standard profile set — a new developer's machine is ready in one run.
Cost and audit built in
The SQLite ledger and CSV export feed FinOps directly; audit hooks send every tool call to a central log. Managers see spend before the invoice.
The commands
#!/usr/bin/env bash
set -euo pipefail
curl -fsSL https://raw.githubusercontent.com/neul-labs/ringlet/main/install.sh | sh
ringlet registry add team https://github.com/yourco/ringlet-registry
ringlet profiles create claude default --provider company-gateway
ringlet profiles create codex scripts --provider company-gateway
ringlet hooks add --all-profiles --on tool-use \
--webhook 'https://audit.yourco.com/agents'
echo "Ready. Run 'ringlet profiles run default' to start."