tribes-login

Runs tribes-cli login in the background and surfaces the browser approval URL until the token persists.

1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/tribes-protocol/trading-harness --skill tribes-login-tribes-protocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tribes-login
Source: https://github.com/tribes-protocol/trading-harness/tree/main/skills/tribes-login
Command: npx skills add https://github.com/tribes-protocol/trading-harness --skill tribes-login-tribes-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authenticating a Tribes agent requires running a blocking CLI login that hides its browser-approval URL for up to three minutes, which fails silently in headless or sandboxed sessions. This Skill runs the login flow in the background, surfaces the approval link immediately, and watches until the API_BEARER_TOKEN is persisted to .env. ## Core Features & Use Cases - Background login orchestration: Launches tribes-cli login with nohup so the approval URL is never hidden behind a blocking foreground process. - Immediate URL surfacing: Polls the login log and sends the user the browser-approval link the moment it appears, even when auto-open fails in sandboxes. - Completion and failure detection: Watches the process until exit, verifies the token landed in .env, and retries the whole flow at most once on timeout or missing token. - Use Case: A fresh sandboxed agent environment has no credentials. Invoke this Skill to get a login link, approve it in your browser, and have the agent confirm it can now trade and check balances. ## Quick Start Ask the agent to log you into Tribes, then open the approval link it sends you and approve it in your browser.

Frequently Asked Questions about tribes-login

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log in to Tribes from a CLI or coding agent?▼

Run tribes-cli login, which prints a browser approval URL and polls for approval with a 3-minute timeout. On success it persists API_BEARER_TOKEN to .env, which the CLI auto-loads for all subsequent commands.

Why does the Tribes login URL never appear in my sandbox?▼

In sandboxed or headless sessions the browser auto-open fails silently, and a foreground login blocks for up to 3 minutes hiding the URL. Run login in the background with nohup and grep the log for the https URL to surface it immediately.

What should I do when Tribes login times out waiting for approval?▼

A timeout means the old approval link is dead. Rerun the login procedure once to mint a fresh URL; if the second attempt also fails, stop and report the failure rather than retrying further.

How do I fix unauthorized or expired token errors on tribes-cli commands?▼

Run tribes-cli login directly to mint a fresh API_BEARER_TOKEN, then retry the failed command once. This mid-session recovery path is separate from the full guided login flow.

How can I verify the Tribes login actually saved the token?▼

Check that .env contains an API_BEARER_TOKEN line, for example with grep -c '^API_BEARER_TOKEN=' .env printing 1. If the login exited cleanly but the token is missing, treat it as a failure and rerun once.