Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.duvo.ai/llms.txt

Use this file to discover all available pages before exploring further.

The CLI stores credentials as named profiles — each holds either an OAuth session or an API key, so you can switch between teams or workspaces without re-entering credentials. This page is the reference for managing those profiles and the teams they act on. For first-time sign-in, see Sign in.

​
Profiles

duvo whoami                          # show the active profile, its key prefix, and team
duvo profiles list                   # list all stored profiles (the default is marked)
duvo profiles use [name]             # switch the default profile (interactive picker if name omitted)
duvo profiles rename <old> <new>     # rename a profile, preserving its credentials
duvo profiles remove <name>          # remove a profile locally

​
Use a different profile for a single command

duvo agents list --profile staging
--profile <name> works on every command and doesn’t change your default.

​
Sign out

duvo logout                          # sign out of the active profile
duvo logout --name <profile>         # sign out of a specific profile
duvo logout --all                    # sign out of every stored profile
duvo logout revokes the OAuth tokens server-side and removes the profile locally.

​
Environment variables

For non-interactive use (CI, scripts), the CLI also reads:
VariableDescription
DUVO_API_KEYAPI key — bypasses the stored profile entirely
DUVO_PROFILEProfile name to use instead of the default

​
Teams

A profile’s credentials are scoped to a team. Use these commands to confirm which team you’re acting on and inspect its members before running commands that change data. 
duvo team current                                                  # the team scoped to your active credentials
duvo team get                                                      # full details for that team
duvo team use <team-id>                                            # set the team for the active profile
duvo team members [--team <team-id>] [--limit <n>] [--offset <n>]  # list team members
duvo teams list                                                    # list every team your credentials can act on
If --team is omitted, member listing uses the team scoped to your API key or active profile. Add --json to any command for machine-readable output.

​
Confirm your team before a destructive command

duvo team current --json | jq -r '.team.name'
Running this first is a cheap way to make sure a bulk delete or delegate lands on the team you intend.