Tools in {{activeName}}
Call any of these with no key on your machine. Copy a snippet, or Try it here.
Register an upstream API here, then call it with no key on your machine.
| {{t.name}} | {{t.host}} | ⌘ run{{t.cli.enabled?'':' off'}}serverlocal-only{{w.label}} |
| {{r.name}} | treg skill install {{r.name}} | ||
Nothing here{{q?' matches "'+q+'"':' yet'}}. This is your personal space - your team's tools live under another org. Switch to a team →
Set up your skills & secrets vault
Nothing registered yet. Load what you already have — your .env keys and skill folders — and they appear here as callable tools.
curl -fsSL {{proxy}}/install.sh | sh treg login
treg onboard # then pick 1 · Setup
Tip — or skip the guide and do it directly:
# preview what's here (read-only) treg scan # register keys + skills treg upload --all
Paste into Claude Code / Codex / Gemini — it installs the CLI, signs in, and registers your skills + keys (with a read-only scan you approve first).
{{buildAgentPrompt('admin', true)}}{{detail.name}} {{detail.kind==='skill' ? 'skill' : (detailData&&detailData.cli ? 'endpoint + CLI' : 'endpoint')}} {{detailData.owner}}
Loading…
Use with your agent
Send someone this page's link, or paste this into a coding agent (Claude Code / Codex / Gemini) — it installs the CLI, signs them in as themselves, and pulls just this skill. Its credential{{detailData.secrets.length>1?'s stay':' stays'}} server-side — calls go through the proxy, no key lands on their machine.
{{detailPrompt}}
Use with your agent
Send someone this page's link, or paste this into a coding agent. Calls go through the proxy — the credential is injected server-side, never on their machine.
{{detailPrompt}}
{{detailData.base_url}}
{{w.label}} injected server-side on every call — the value never appears here or on a caller's machine.
none — a public upstream, no credential needed.
treg run {{detail.name}} -- <args> server local-only ⌘ run off
runs matching these patterns are refused before the key is injected: {{p}}
▚ {{detailParentSkill.name}} — the recipe + files that registered this tool.
Secrets in {{activeName}}
The credentials your tools inject. Values are encrypted server-side and never shown.
| {{s.name}} | {{s.kind}} | owner: {{short(s.owner)}} |
No secrets yet — add one below, or bulk-load everything at once (setup guide under the form).
Tip: paste a whole .env into the name field — it splits into rows automatically.
A param is non-secret config (project id, org id) — injected alongside a credential into CLI env or an HTTP query.
Set up your skills & secrets vault
Bulk-load your keys (and skills) from your machine — each lands here encrypted, referenced by name.
curl -fsSL {{proxy}}/install.sh | sh treg login
treg onboard # then pick 1 · Setup
Tip — or skip the guide and do it directly:
# preview what's here (read-only) treg scan # register keys + skills treg upload --all
Paste into Claude Code / Codex / Gemini — it installs the CLI, signs in, and registers your skills + keys (with a read-only scan you approve first).
{{buildAgentPrompt('admin', true)}}{{activeName}} {{activeRole}}personal
Team settings · your personal space. Switch, create, or join teams from the sidebar.
You're {{activeRole}} in {{activeName}}. Members & invites are visible to admins.
Your usage today: {{myUsage.used_today}} / {{myUsage.cap}} calls.
Daily cap = how many calls + runs a member may make per day. -1 = unlimited.
Tools = which endpoints/CLIs a member may call or run. Local run = may run CLIs on their own machine (off = server only). The owner always has full access.
| Role | Today | Daily cap | Tools | Local run | ||
|---|---|---|---|---|---|---|
| {{m.email}} | {{m.role}} | {{m.used_today}} | All | |||
|
Tools & skills {{m.email}} may use/see — uncheck to withhold. All checked = full access (and new ones apply automatically).
No tools registered yet.
|
||||||
{{lastInvite.code}}| Role | Invited by | Expires | ||
|---|---|---|---|---|
| {{inv.email}} | {{inv.role}} | {{short(inv.invited_by)}} | {{inv.expires_at?until(inv.expires_at):'never'}} |
No pending invites.
Activity - {{activeName}}
Every proxy call and server CLI run in this org.
| When | Who | Tool | Action | Status |
|---|---|---|---|---|
| {{when(a.created_at)}} | {{short(a.user_email)}} | {{a.tool}} | {{a.where||'run'}}{{a.action}} | {{a.status}} |
No activity yet.
Usage - {{activeName}}
Calls & runs per member over the last {{usageDays}} days. Counts only - no request or response content is stored.
| Member | API | Local | Server | Total |
|---|---|---|---|---|
| {{short(u.user_email)}} | {{u.call}} | {{u.local_run}} | {{u.server_run}} | {{u.total}} |
No usage in this window.
| Tool | Events |
|---|---|
| {{t.name}} | {{t.total}} |
| Day | Events |
|---|---|
| {{d.day}} | {{d.total}} |
Loading…
Platform admin
Cross-tenant control (super-admin). Suspend locks members out; delete cascades.
| Org | Members | Tools | Status | |
|---|---|---|---|---|
| {{o.name}} | {{o.members}} | {{o.tools}} | {{o.suspended?'suspended':'active'}} |
| Orgs | Flags | ||
|---|---|---|---|
| {{u.email}}you | {{u.orgs.length}} | super-admin suspended - | - you - |
Getting started
Share your skills & API keys with the team. Fastest — hand your coding agent the instruction below; it installs the CLI, signs in, and registers your local skills + keys as shared tools (with a read-only scan you approve first).
{{buildAgentPrompt('admin', true)}}Two ways to give your agents power: share a whole skill, or register a single API endpoint. Everything here works in this dashboard too - this is the CLI path. Grab it as markdown ↑ to paste anywhere.
Installs the treg command and points it at this server. Upgrade later with treg update.
curl -fsSL {{proxy}}/install.sh | sh
Opens your browser - GitHub or an email code. Your first sign-in also registers you.
treg loginGuided: scans your .env + skill folders, you pick what to share, and it registers them in one pass.
treg onboard # then pick 1 · Setup
Register your .env keys and skill folders without the guided flow. Idempotent — re-run freely.
treg upload # both .env + skills in this dir treg upload env --select openai,stripe treg upload skills --dir ~/.claude/skills --all # register skill from a specific path
Use the team's shared skills & tools from your terminal or agent — pull a skill, call any tool, with no API keys on your machine.
Paste into Claude Code / Codex / Gemini. It pulls the team's shared skills and makes a test call — no API keys land on your machine.
{{buildAgentPrompt('consumer', true)}}Installs the treg command and points it at this server.
curl -fsSL {{proxy}}/install.sh | sh
Opens your browser — GitHub, Google, or an email code.
treg loginLists the team's tools + skills, installs the ones you pick, and makes a no-key test call.
treg onboard # then pick 2 · Connect existing tool-registry
Browse the shared library, pull a skill, and call a tool — the key stays in the vault, never on your machine.
treg skill ls treg skill install seo-blog-writer treg call https://api.stripe.com/v1/charges
Tutorial
Five ways to learn treg - pick one.
✨ Guided setup
Seed a demo team - teammates, a working tool, live activity - and walk it in 3 beats. Learn by doing.
▤ CLI tutorial
The whole registry from your terminal - copy each command and follow along. {{tutSteps.length}} steps.
▚ Dashboard tour
Everything you can do in this web UI, a screenshot per step. {{tourSteps.length}} steps.
▞ Import & shell
Turn the CLIs on your machine into team tools, then use them in a shell where they just work - plus the security sandbox. {{(tutData.importShell||[]).length}} steps.
▟ Team access control
Choose which tools each member may use, and whether they may run CLIs locally. {{(tutData.access||[]).length}} steps.
Tried the demo? Remove demo teammates →
CLI tutorial
| Action | {{c}} |
|---|---|
| {{r[0]}} | {{v?'✔':'✘'}} |