Install
Global install with npm.
$npm install -g @tribanai/cliTRIBAN CLI · Preview
Your security agent, in the terminal
Plan, scan, review and report from bash, zsh or PowerShell. Every action stays inside your scope file and is logged.
$npm install -g @tribanai/cliPreview build · commands go live at launch
triban — zsh — 80×24
QUICK START
Up and running in three commands
Sign in
Opens your browser. Google, GitHub or email.
$triban loginStart
Creates scope.yaml and opens a session.
$triban init --scope && triban chatREFERENCE
Commands
Session
triban chat
Start an interactive session
$triban chattriban chat --cloud
Run in a cloud sandbox
$triban chat --cloudtriban sessions
List sessions
$triban sessionstriban resume <id>
Reopen a session
$triban resume s_8f2aScope
triban init --scope
Create scope.yaml
$triban init --scopetriban scope show
Print current scope
$triban scope showtriban scope validate
Check targets, expiry and signer
$triban scope validateWork · Inside a session
/recon <target>
Passive recon on in-scope assets
$/recon api.example.in/scan
Dependency & config scan
$/scan/review
Security code review
$/review/forensics <file>
Parse logs, extract IOCs, build a timeline
$/forensics auth.log/report [md|pdf]
Export findings
$/report pdfModels
/model <name>
Switch model
$/model triban-securitytriban chat --model triban-security --effort high
Start a session with a specific model and effort
$triban chat --model triban-security --effort highAutomation
triban run --headless --task review-pr --pr 42
Review a pull request in CI and post findings as comments
$triban run --headless --task review-pr --pr 42Account
triban login
Sign in
$triban logintriban logout
Sign out
$triban logouttriban whoami
Show the signed-in account
$triban whoamitriban update
Update the CLI
$triban updateDEPLOYMENT
Runs where you work
Local
Runs on your machine. Code stays local unless you choose a cloud session.
Cloud
An isolated sandbox per session, deleted when the session ends.
CI/CD
Headless mode reviews every pull request and posts findings as comments.
Agents refuse out-of-scope targets
Every command is checked against scope.yaml before it runs. Blocked actions are logged with the reason, so your client and your auditor can see exactly what was and wasn't touched.
scope guard
› /recon payments.example-client.in
✕ Blocked: payments.example-client.in is excluded in scope.yaml (line 6)
↳ Ask the scope owner to update scope.yaml, or pick an in-scope target.
✓ Logged to audit trail · event a91f
- bash
- zsh
- fish
- PowerShell
- Windows Terminal
- iTerm2
- VS Code terminal
FAQ
CLI questions
What is the TRIBAN CLI?
A command-line agent for security and coding work. You describe the task; it plans, runs tools inside your authorized scope, and returns findings, patches and a report. It runs on your machine or in a TRIBAN cloud sandbox.
What is a scope file and why is it required?
A scope file (scope.yaml) lists the targets you are authorized to test, what is excluded, who authorized it and when it expires. Agents refuse to act on anything outside it, and every action is logged against it.
How are the Web Console, Web Terminal and CLI different?
Web Console: chat and investigations in the browser. Web Terminal: a cloud terminal inside the console, nothing to install. CLI: the same agent on your own machine or in CI. Sessions, scope files and settings sync across all three.
Which operating systems does the CLI support?
Windows 10/11 (x64), macOS 13+ (Apple Silicon and Intel) and Linux (x64 and arm64). The Web Terminal works in any modern browser.