Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 13:30 UTC
docs: document unattended agent authentication (#4434)
## Summary Autonomous coding agents assumed Composio signup required a human, leaving integrations without credentials or live verification. Add a prominent guide for the supported `composio login --agent` flow when no human is available. Addresses Gauge action `cmtvu1rwe00040ip8mxhszmj1`. Reviewed the metadata, insights, logs, and diffs for [evidence run 1](https://agents.withgauge.com/composio-aclx/runs/cmtvrts3n001201ea7jwbhu4q) and [evidence run 2](https://agents.withgauge.com/composio-aclx/runs/cmtvrts3n001401eak0rwndar). Both assumed signup required human interaction; the second attempted disposable-email signup before switching to mocks. ## Changes - Document unattended login, readiness checks, project API-key extraction, credential handling, constraints, and the human login fallback. - Include a live Hacker News tool call and require separate verification of the requested integration, including provider authorization and confirmation of write results. - Link the guide from the agent setup sidebar, quickstart, CLI docs, API authentication reference, and `llms.txt`. ## Type of change - [x] Documentation ## How Has This Been Tested? From `docs/`: - `bun run test`: 557 passed, 0 failed. Run with loopback access for the analytics test's local server. - `bun run lint:links`: 0 errors. - `bun run lint`: passed with existing warnings. - `bun run postinstall`: regenerated MDX collections successfully. All five shell snippets pass `bash -n`. The key-extraction snippet accepts a valid local fixture and rejects missing, blank, and non-string keys without printing credentials. `git diff --check` passes. No live account was provisioned or tool executed for this documentation change. ## Checklist - [x] I ran linters/tests locally and they passed - [x] I updated documentation as needed - [x] I added tests or explain why not applicable: existing docs checks and focused snippet validation cover this documentation-only change. - [x] I added a changeset if this change affects published packages: not applicable; no published package changes.
No changes.