composio-cli

# Composio CLI ## Preflight: Is The User Logged In? **Before running any toolkit command, confirm the user is logged in. If they are not, stop and tell them to log in — do not improvise.** ```bash composio whoami # exits non-zero when there is no session ``` If `whoami` fails (no Composio session), the user is logged out. **Stop here.** Do not: - run `composio login` yourself, - look for an alternate toolkit, slug, or `proxy` route, - ask the user to paste a key, or - attempt any other workaround. Respond directly to the user with one message: they need to log in to Composio first, via the **"Log in with Composio"** action on the Composio app's dashboard. Then end your turn and wait — the request cannot proceed until they have logged in. Only once `whoami` succeeds do you continue to the workflow below. ## Connection Invariant: One Account Per Toolkit Rome operates **exactly one connected account per toolkit**. This is load-bearing because `execute`, `proxy`, and `run` have **no flag to choose an account** — they act on the toolkit's single connected account, and when more than one exists Composio silently resolves a non-deterministic default. You cannot tell, and cannot control, which account a tool ran as. A second Gmail means a "send email" might go out from the wrong account with no signal. To keep every tool call deterministic: - **Never create a second account for a toolkit.** Do not pass `--alias` to `composio link` to add an additional account, and do n...