zilmate 1.7.8 → 1.8.0

package/.agents/skills/chat-sdk/SKILL.md

@@ -0,0 +1,240 @@
+---
+name: chat-sdk
+description: Build multi-platform chat bots with Chat SDK (`chat` npm package). Use when developers want to scaffold a bot with create-chat-sdk, build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI streaming, set up webhook routes or multi-adapter bots, send rich cards or streamed AI responses to chat platforms, or build a custom adapter or state adapter.
+---
+
+# Chat SDK
+
+Unified TypeScript SDK for building chat bots across Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, and WhatsApp. Write bot logic once, deploy everywhere.
+
+## Scaffold a new project
+
+Use `create-chat-sdk` with explicit adapters so coding agents can scaffold a webhook-only Next.js bot project without prompts:
+
+```bash
+npm create chat-sdk@latest -- my-bot --adapter slack memory -y
+```
+
+Non-interactive example:
+
+```bash
+npm create chat-sdk@latest -- my-bot --adapter slack redis -d "My bot" --pm pnpm -y
+```
+
+With npm, the `--` separator is required — npm consumes the flags itself instead of forwarding them to the CLI. `pnpm create` and `yarn create` forward flags without it.
+
+Key flags:
+- `--adapter <values...>` — platform or state adapters from `chat/adapters`
+- `-d, --description <text>` — project description
+- `--pm <manager>` — package manager (`npm`, `yarn`, `pnpm`, `bun`)
+- `-y, --yes` — skip prompts and accept defaults
+- `--interactive` — always prompt, even when a coding agent environment is detected
+- `-f, --force` — overwrite generated files in an existing directory
+- `-s, --skip-install` — skip dependency installation
+- `--no-git` — skip git repository initialization
+- `-q, --quiet` — suppress non-essential output
+
+When `create-chat-sdk` detects a coding agent environment, it automatically uses non-interactive defaults. Pass at least one platform adapter with `--adapter`; the state adapter defaults to `memory`. If no project name is provided, it uses `my-bot`.
+
+Generated projects include `src/lib/bot.ts`, `src/app/api/webhooks/[platform]/route.ts`, `.env.example`, `next.config.ts`, and adapter dependencies. If the Web adapter is selected, the CLI also creates `src/app/api/chat/route.ts` and `src/lib/auth-stub.ts`.
+
+## Start with published sources
+
+When Chat SDK is installed in a user project, inspect the published files that ship in `node_modules`:
+
+```
+node_modules/chat/docs/                    # bundled docs
+node_modules/chat/dist/index.d.ts          # core API types
+node_modules/chat/dist/adapters/index.d.ts # static adapter catalog types
+node_modules/chat/dist/jsx-runtime.d.ts    # JSX runtime types
+node_modules/chat/docs/contributing/       # adapter-authoring docs
+node_modules/chat/resources/guides/        # framework/platform guides (markdown)
+node_modules/chat/resources/templates.json # starter templates (title, description, href)
+```
+
+If one of the paths below does not exist, that package is not installed in the project yet.
+
+Read these before writing code:
+- `node_modules/chat/docs/getting-started.mdx` — install and setup
+- `node_modules/chat/docs/usage.mdx` — `Chat` config and lifecycle
+- `node_modules/chat/docs/handling-events.mdx` — event routing and handlers
+- `node_modules/chat/docs/threads-messages-channels.mdx` — thread/channel/message model
+- `node_modules/chat/docs/posting-messages.mdx` — post, edit, delete, schedule
+- `node_modules/chat/docs/streaming.mdx` — AI SDK integration and streaming semantics
+- `node_modules/chat/docs/cards.mdx` — JSX cards
+- `node_modules/chat/docs/actions.mdx` — button/select interactions
+- `node_modules/chat/docs/modals.mdx` — modal submit/close flows
+- `node_modules/chat/docs/slash-commands.mdx` — slash command routing
+- `node_modules/chat/docs/direct-messages.mdx` — DM behavior and `openDM()`
+- `node_modules/chat/docs/files.mdx` — attachments/uploads
+- `node_modules/chat/docs/state-adapters.mdx` — persistence, locking, dedupe
+- `node_modules/chat/docs/adapters.mdx` — cross-platform feature matrix
+- `node_modules/chat/docs/api/chat.mdx` — exact `Chat` API
+- `node_modules/chat/docs/api/thread.mdx` — exact `Thread` API
+- `node_modules/chat/docs/api/message.mdx` — exact `Message` API
+- `node_modules/chat/docs/api/modals.mdx` — modal element and event details
+
+For the specific adapter or state package you are using, inspect that installed package's `dist/index.d.ts` export surface in `node_modules`.
+
+## Adapter catalog subpath
+
+Chat SDK exposes a zero-dependency static catalog at `chat/adapters`. Agents can import `ADAPTERS`, `ADAPTER_NAMES`, `getAdapter`, `isAdapterSlug`, `listEnvVars`, `getSecretEnvVars`, and metadata types like `CatalogAdapter` and `AdapterSlug` from this subpath without importing any adapter implementation package.
+
+Use it for:
+- Listing official and vendor-official adapter slugs, names, npm packages, groups, and platform vs state types.
+- Building setup or onboarding flows that need package names, peer dependencies, and install guidance before any adapter is installed.
+- Discovering required, optional, and credential-mode environment variables for an adapter, including which variables are secrets.
+- Keeping vendor-official adapter docs and metadata aligned with the catalog when adding or updating a listed adapter.
+
+## Available resources
+
+<!-- RESOURCES:START -->
+
+### Guides
+
+- `node_modules/chat/resources/guides/how-to-build-an-ai-agent-for-slack-with-chat-sdk-and-ai-sdk.md` — Build a Slack AI agent using Chat SDK, AI SDK's ToolLoopAgent, and Vercel AI Gateway. Covers project setup, tool definitions, streaming responses, deployment to Vercel, and scaling tool selection with toolpick.
+- `node_modules/chat/resources/guides/human-in-the-loop-with-chat-sdk-and-workflow-sdk.md` — Pause durable workflows on Slack approval cards using Chat SDK and Workflow SDK. Uses createWebhook to suspend workflows until a button click, with patterns for multi-stage approvals, timeouts via durable sleep, and approver validation.
+- `node_modules/chat/resources/guides/liveblocks-chat-sdk-ai-sdk.md` — Build an AI agent that replies to @-mentions in Liveblocks comment threads with streamed responses and tool calling. Uses Chat SDK, the Liveblocks adapter, AI SDK's ToolLoopAgent, and Redis for thread subscriptions and distributed locking.
+- `node_modules/chat/resources/guides/slack-bot-vercel-blob.md` — Build a Slack bot that lists, reads, uploads, and deletes files in Vercel Blob through tool calls. Uses Chat SDK, AI SDK's ToolLoopAgent, and Files SDK's createFileTools factory with approval-gated write tools and a read-only mode.
+- `node_modules/chat/resources/guides/run-and-track-deploys-from-slack.md` — Build a Slack deploy bot with Chat SDK and Vercel Workflow. Dispatch GitHub Actions from a slash command, gate production behind approval, poll for completion, and notify Linear and GitHub when the run finishes.
+- `node_modules/chat/resources/guides/triage-form-submissions-with-chat-sdk.md` — Build a Slack bot that triages form submissions with interactive cards. Forward, edit, or mark as spam without leaving Slack. Built with Chat SDK, Hono, and Resend.
+- `node_modules/chat/resources/guides/how-to-build-a-slack-bot-with-next-js-and-redis.md` — This guide walks through building a Slack bot with Next.js, covering project setup, Slack app configuration, event handling, interactive features, and deployment.
+- `node_modules/chat/resources/guides/create-a-discord-support-bot-with-nuxt-and-redis.md` — This guide walks through building a Discord support bot with Nuxt, covering project setup, Discord app configuration, Gateway forwarding, AI-powered responses, and deployment.
+- `node_modules/chat/resources/guides/ship-a-github-code-review-bot-with-hono-and-redis.md` — This guide walks through building a GitHub bot that reviews pull requests on demand. When a user @mentions the bot on a PR, Chat SDK picks up the mention, spins up a Vercel Sandbox with the repo cloned, and uses AI SDK to analyze the diff.
+- `node_modules/chat/resources/guides/build-a-slack-bot-with-vercel-connect.md` — Learn how to build your very own Slackbot with Chat SDK and AI SDK. Vercel Connect supplies runtime Slack tokens and forwards triggers, so you never store a long-lived bot token.
+- `node_modules/chat/resources/guides/vercel-connect.md` — Use Vercel Connect to call provider APIs like Slack, GitHub, and Snowflake from your agents and services with short-lived, user-authorized tokens instead of long-lived secrets.
+- `node_modules/chat/resources/guides/ai-gateway-and-ai-sdk.md` — Build AI agents on Vercel with AI Gateway and AI SDK, then make them reliable, capable, and durable with Sandbox, Chat SDK, Vercel Connect, and Workflow.
+- `node_modules/chat/resources/guides/daily-digest-bot-with-chat-sdk-and-workflow-sdk.md` — Create your own daily digest bot that posts a daily digest of GitHub stats to Slack. Learn how to use Vercel Connect to set up Slack and GitHub app securely in your project.
+
+### Templates
+
+Listed in `node_modules/chat/resources/templates.json`:
+
+- **Chat SDK Liveblocks Bot** — Build a bot that you can engage with inside Liveblocks. (https://vercel.com/templates/next.js/chat-sdk-liveblocks-bot)
+- **Durable iMessage Agent** — Durable iMessage agent powered by the Sendblue adapter. (https://vercel.com/templates/nitro/durable-imessage-ai-agent)
+- **Knowledge Agent** — Open source file-system and knowledge based agent template. Build AI agents that stay up to date with your knowledge base. (https://vercel.com/templates/nuxt/chat-sdk-knowledge-agent)
+- **Community Agent** — Open source AI-powered Slack community management bot with a built-in Next.js admin panel. Uses Chat SDK, AI SDK, and Vercel Workflow. (https://vercel.com/templates/next.js/chat-sdk-community-agent)
+- **Caltext** — iMessage calorie tracking assistant powered by AI. (https://vercel.com/templates/hono/caltext)
+
+<!-- RESOURCES:END -->
+
+## Quick start
+
+```typescript
+import { Chat } from "chat";
+import { createSlackAdapter } from "@chat-adapter/slack";
+import { createRedisState } from "@chat-adapter/state-redis";
+
+const bot = new Chat({
+  userName: "mybot",
+  adapters: {
+    slack: createSlackAdapter(),
+  },
+  state: createRedisState(),
+  dedupeTtlMs: 600_000,
+});
+
+bot.onNewMention(async (thread) => {
+  await thread.subscribe();
+  await thread.post("Hello! I'm listening to this thread.");
+});
+
+bot.onSubscribedMessage(async (thread, message) => {
+  await thread.post(`You said: ${message.text}`);
+});
+```
+
+## Core concepts
+
+- **Chat** — main entry point; coordinates adapters, routing, locks, and state
+- **Adapters** — platform-specific integrations for Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, and WhatsApp
+- **State adapters** — persistence for subscriptions, locks, dedupe, and thread state
+- **Thread** — conversation context with `post()`, `stream()`, `subscribe()`, `setState()`, `startTyping()`
+- **Message** — normalized content with `text`, `formatted`, attachments, author info, and platform `raw`
+- **Channel** — container for threads and top-level posts
+
+## Event handlers
+
+| Handler | Trigger |
+|---------|---------|
+| `onNewMention` | Bot @-mentioned in an unsubscribed thread |
+| `onDirectMessage` | New DM in an unsubscribed DM thread |
+| `onSubscribedMessage` | Any message in a subscribed thread |
+| `onNewMessage(regex)` | Regex match in an unsubscribed thread |
+| `onReaction(emojis?)` | Emoji added or removed |
+| `onAction(actionIds?)` | Button clicks and select/radio interactions |
+| `onModalSubmit(callbackId?)` | Modal form submitted |
+| `onModalClose(callbackId?)` | Modal dismissed/cancelled |
+| `onSlashCommand(commands?)` | Slash command invocation |
+| `onAssistantThreadStarted` | Slack assistant thread opened |
+| `onAssistantContextChanged` | Slack assistant context changed |
+| `onAppHomeOpened` | Slack App Home opened |
+| `onMemberJoinedChannel` | Slack member joined channel event |
+
+Read `node_modules/chat/docs/handling-events.mdx`, `node_modules/chat/docs/actions.mdx`, `node_modules/chat/docs/modals.mdx`, and `node_modules/chat/docs/slash-commands.mdx` before wiring handlers. `onDirectMessage` behavior is documented in `node_modules/chat/docs/direct-messages.mdx`.
+
+## Streaming
+
+Pass any `AsyncIterable<string>` to `thread.post()`. For AI SDK, prefer `result.fullStream` over `result.textStream` when available so step boundaries are preserved.
+
+```typescript
+import { ToolLoopAgent } from "ai";
+
+const agent = new ToolLoopAgent({ model: "anthropic/claude-4.5-sonnet" });
+
+bot.onNewMention(async (thread, message) => {
+  const result = await agent.stream({ prompt: message.text });
+  await thread.post(result.fullStream);
+});
+```
+
+Key details:
+- `streamingUpdateIntervalMs` controls post+edit fallback cadence
+- `fallbackStreamingPlaceholderText` defaults to `"..."`; set `null` to disable
+- Structured `StreamChunk` support is Slack-only; other adapters ignore non-text chunks
+
+## Cards and modals (JSX)
+
+Set `jsxImportSource: "chat"` in `tsconfig.json`.
+
+Card components:
+- `Card`, `CardText`, `Section`, `Fields`, `Field`, `Button`, `CardLink`, `LinkButton`, `Actions`, `Select`, `SelectOption`, `RadioSelect`, `Table`, `Image`, `Divider`
+
+Modal components:
+- `Modal`, `TextInput`, `Select`, `SelectOption`, `RadioSelect`
+
+`Button` and `Modal` accept a `callbackUrl` prop — when triggered, the SDK POSTs the action payload to that URL in addition to firing any `onAction` / `onModalSubmit` handler. Use this for webhook-based workflow flows. See `node_modules/chat/docs/actions.mdx` and `node_modules/chat/docs/modals.mdx`.
+
+```tsx
+await thread.post(
+  <Card title="Order #1234">
+    <CardText>Your order has been received.</CardText>
+    <Actions>
+      <Button id="approve" style="primary">Approve</Button>
+      <Button id="reject" style="danger">Reject</Button>
+    </Actions>
+  </Card>
+);
+```
+
+## Adapter inventory
+
+See [chat-sdk.dev/adapters](https://chat-sdk.dev/adapters) for the current list of official, vendor-official, and community adapters, including package names and authors. For the exact factory function and config types of an installed adapter, inspect its `dist/index.d.ts` in `node_modules`.
+
+## Building a custom adapter
+
+Read these published docs first:
+- `node_modules/chat/docs/contributing/building.mdx`
+- `node_modules/chat/docs/contributing/testing.mdx`
+- `node_modules/chat/docs/contributing/publishing.mdx`
+
+Also inspect:
+- `node_modules/chat/dist/index.d.ts` — `Adapter` and related interfaces
+- `node_modules/@chat-adapter/shared/dist/index.d.ts` — shared errors and utilities
+- Installed official adapter `dist/index.d.ts` files — reference implementations for config and APIs
+
+A custom adapter needs request verification, webhook parsing, message/thread/channel operations, ID encoding/decoding, and a format converter. Use `BaseFormatConverter` from `chat` and shared utilities from `@chat-adapter/shared`.
+
+## Webhook setup
+
+Each registered adapter exposes `bot.webhooks.<name>`. Wire those directly to your HTTP framework routes. See `node_modules/chat/resources/guides/how-to-build-a-slack-bot-with-next-js-and-redis.md` and `node_modules/chat/resources/guides/create-a-discord-support-bot-with-nuxt-and-redis.md` for framework-specific route patterns.

package/.agents/skills/composio/AGENTS.md

@@ -0,0 +1,404 @@
+---
+name: composio
+description: Use 1000+ external apps via Composio - either directly through the CLI or by building AI agents and apps with the SDK
+tags: [composio, tool-router, agents, mcp, tools, api, automation, cli]
+---
+
+# composio
+
+Use 1000+ external apps via Composio - either directly through the CLI or by building AI agents and apps with the SDK
+
+## When to Apply
+- User wants to access or interact with external apps (Gmail, Slack, GitHub, Notion, etc.)
+- User wants to automate a task using an external service (send email, create issue, post message)
+- Building an AI agent or app that integrates with external tools
+- Multi-user apps that need per-user connections to external services
+
+## Table of Contents
+
+1. [Use Apps via Composio CLI](#use-apps-via-composio-cli)
+   1.1. [Composio CLI Guide](#composio-cli-guide)
+
+2. [Building Apps and Agents with Composio](#building-apps-and-agents-with-composio)
+   2.1. [Building with Composio](#building-with-composio)
+
+---
+
+## 1. Use Apps via Composio CLI
+
+<a name="use-apps-via-composio-cli"></a>
+
+### 1.1. Composio CLI Guide
+
+<a name="composio-cli-guide"></a>
+
+**Impact:** 🟠 HIGH
+
+> Use the Composio CLI to take actions on external apps directly - no code needed
+
+# Composio CLI Guide
+
+Use the Composio CLI to search, connect, and execute tools directly — no code writing required. Ideal for agents taking actions on behalf of the user.
+
+## Prerequisites (first-time setup)
+
+If the CLI is not installed or the user is not authenticated:
+
+```bash
+# Install
+curl -fsSL https://composio.dev/install | bash
+composio --version   # verify
+
+# Authenticate
+composio login       # OAuth flow; interactive org/project picker after login (use -y to skip)
+composio whoami      # verify org_id, project_id, user_id (API keys are never displayed)
+# Run upgrade in case you run into errors or starting with a new project
+composio upgrade
+```
+
+> **Note**: Use `whoami` only to verify login status — do not hardcode these values in code. `whoami` shows hints for `composio manage orgs switch` and `composio init` when relevant.
+
+**Login behavior**: By default, `composio login` shows an interactive org/project picker after OAuth. Use `composio login -y` to skip the picker and use session defaults. JSON output is emitted only after the picker finishes (or immediately with `-y`), so piped/scripted usage gets the correct `org_id` and `project_id`.
+
+**Agent login (no direct browser access)**: For agents that cannot open a browser for the user, use a two-step flow:
+
+1. **Get login URL and session key** — Print login URL and JSON (jq-parseable) then exit without opening browser or waiting:
+   ```bash
+   composio login --no-wait | jq
+   ```
+   Share the login URL with the agent's user to complete login in their browser.
+
+2. **Complete login with session key** — Use the `key` from the previous output to check if the user has logged in:
+   ```bash
+   composio login --key "<key>"
+   ```
+   Without `--no-wait`: polls until the session is linked (same as browser flow after printing URL).
+   With `--no-wait`: checks once and fails if not linked. For agents, once the user completes login, run with `--no-wait` to avoid blocking.
+
+## Primary Workflow: search → link → execute
+
+### Step 1 — Find the right tool
+
+```bash
+composio search "send an email"
+composio search "create github issue"
+composio search "post slack message"
+```
+
+The search results include connection status, so you can see immediately if the user is already connected to the required app.
+
+> **Important**: Do not trim the output of `composio search` (e.g. with `head`). Use the full results to pick the right tool — truncating can hide the best match.
+
+### Step 2 — Connect an account (if needed)
+
+If the user is not connected to the app, link their account:
+
+```bash
+composio link gmail
+composio link github
+composio link slack
+```
+
+This opens an OAuth flow or prompts for credentials. Only needed once per app. By default, `composio link` waits until the connected account is ACTIVE (opens browser, polls). Use `--no-wait` for scripted or agent usage: it prints link info and JSON to stdout (JQ-friendly) and exits immediately. Output includes `status`, `connected_account_id`, `redirect_url`, and `toolkit`.
+
+### Step 3 — Execute the tool
+
+```bash
+composio execute GMAIL_SEND_EMAIL --data '{"recipient_email":"you@example.com","subject":"Hello","body":"Test"}'
+composio execute GITHUB_CREATE_AN_ISSUE --data '{"owner":"acme","repo":"my-repo","title":"Bug report"}'
+```
+To see a tool's input parameters before executing:
+```bash
+composio execute GMAIL_SEND_EMAIL --help
+```
+
+### Step 4 — Listen for events (optional)
+
+```bash
+composio listen
+```
+
+Streams real-time trigger events to the terminal.
+
+---
+
+## Tips for Agents
+
+- **All commands output JSON** — pipe to `jq` for filtering and extraction
+- **Agent login** — When the agent has no direct browser access, use `composio login --no-wait` to get the URL and key, share the URL with the user, then `composio login --key <key> --no-wait` once they complete login
+- **Parallel execution** — use `&` and `wait` or shell scripts for complex multi-step tasks
+- The default user context is the project's `test_user_id`. Pass `--user-id <id>` to act on behalf of a specific user.
+
+```bash
+composio execute GMAIL_SEND_EMAIL --user-id "user_123" --data '{"recipient_email":"them@example.com","subject":"Hi"}'
+```
+
+## Best Practices
+
+1. **Use `jq` for JSON** — Pipe CLI output to `jq` for filtering and extraction instead of parsing raw JSON.
+2. **Control output at source** — When fetching large amounts of data, use the tool's filters (if supported) to limit what is returned.
+3. **Offload analysis** — After understanding the schema, use inline bash scripts for heavy data analysis instead of manual inspection. Avoid using composio SDK for personal usecases only use the SDKs when building apps.
+4. **Parallelize independent actions** — For tools/actions that don't depend on each other, run them in parallel with `&` and `wait`. Use `xargs -P` or `parallel` only when the backend can handle the load.
+5. **Avoid large terminal dumps** — Filter, search, and summarize instead of outputting full datasets:
+   - Quick text filtering: `grep -E`, `rg` (ripgrep), `awk`, `sed`
+   - Summarize: `sort | uniq -c | sort -nr`, `wc -l`, `head`, `tail`
+   - For large output: `less`, `lnav` (logs), `tail -f` for streaming
+6. **Minimize file creation** — Use ephemeral files only when needed; create files only when the user explicitly asks.
+7. **Respect rate limits** — Be mindful of pagination and API/CLI rate limits when parallelizing.
+8. **Never invent tool slugs or app names** — Only use tools returned by `composio search`. For app names, use `composio manage toolkits info <slug>` or `composio manage tools info <tool>` to verify.
+9. **Do not trim `composio search` output** — Never pipe search results through `head`, `tail`, or similar. Use the full output to find the best tool match.
+
+---
+
+## Advanced Commands
+
+### Discover Tools (when search isn't enough)
+
+```bash
+# List all toolkits
+composio manage toolkits list
+
+# Get details about a specific toolkit
+composio manage toolkits info "gmail"
+
+# List tools in a toolkit
+composio manage tools list --toolkits "gmail"
+
+# Get a tool's full schema
+composio manage tools info "GMAIL_SEND_EMAIL"
+```
+
+### Connected Accounts
+
+```bash
+# List active connections
+composio manage connected-accounts list --status ACTIVE
+
+# Link an account (full form with options)
+composio manage connected-accounts link --auth-config "ac_..." --user-id "user_123"
+
+# Delete a connection
+composio manage connected-accounts delete <id>
+```
+
+### Auth Configs
+
+> Only needed when building apps with custom OAuth credentials. For personal use and agents, `composio link` handles this automatically.
+
+```bash
+composio manage auth-configs list --toolkits "gmail"
+composio manage auth-configs create
+composio manage auth-configs info <id>
+composio manage auth-configs delete <id>
+```
+
+### Triggers
+
+```bash
+# List available trigger types
+composio manage triggers list
+composio manage triggers info "GMAIL_NEW_GMAIL_MESSAGE"
+
+# Manage trigger instances
+composio manage triggers create <trigger-name>
+composio manage triggers enable <id>
+composio manage triggers disable <id>
+composio manage triggers status
+```
+
+### Debugging & Logs
+
+```bash
+# View recent tool executions
+composio manage logs tools
+
+# Get detailed logs for a specific execution
+composio manage logs tools "log_abc123"
+
+# Monitor trigger events
+composio manage logs triggers
+```
+---
+
+## jq Examples
+
+```bash
+# Extract toolkit slugs
+composio manage toolkits list | jq -r '.[].slug'
+
+# Get tool names from a toolkit
+composio manage tools list --toolkits "gmail" | jq -r '.[].name'
+
+# Filter active connections
+composio manage connected-accounts list --status ACTIVE | jq -r '.[].id'
+
+# Extract login URL and key from agent login flow
+composio login --no-wait | jq -r '.login_url'
+composio login --no-wait | jq -r '.key'
+```
+
+## Command Help
+
+Every command supports `--help` for detailed options:
+
+```bash
+composio --help
+composio login --help
+composio search --help
+composio execute --help
+composio link --help
+composio listen --help
+composio manage tools --help
+composio manage toolkits --help
+composio manage triggers --help
+```
+
+---
+
+## 2. Building Apps and Agents with Composio
+
+<a name="building-apps-and-agents-with-composio"></a>
+
+### 2.1. Building with Composio
+
+<a name="building-with-composio"></a>
+
+**Impact:** 🟠 HIGH
+
+> SDK-based guide for building AI agents and applications that integrate with external tools via Composio
+
+# Building Apps and Agents with Composio
+
+Use the Composio SDK to build AI agents, chat apps, and backend services that integrate with 200+ external tools.
+
+## Project Setup
+
+Run inside your project directory to initialize and store the API key:
+```bash
+composio init
+```
+
+## Install the SDK
+
+**TypeScript**
+```bash
+pnpm install @composio/core@latest
+```
+
+Provider packages for agentic frameworks:
+- `@composio/vercel` — Vercel AI SDK
+- `@composio/openai-agents` — OpenAI Agents
+- `@composio/langchain` — LangChain
+- `@composio/mastra` — Mastra
+- `@composio/claude-agent-sdk` — Claude Agent SDK
+
+**Python**
+```bash
+pip install composio
+```
+
+Provider packages for agentic frameworks:
+- `composio-openai-agents` — OpenAI Agents
+- `composio-langchain` — LangChain
+- `composio-langgraph` — LangGraph
+- `composio-crewai` — CrewAI
+- `composio-claude-agent-sdk` — Claude Agent SDK
+- `composio-google-adk` — Google ADK
+
+Pass the provider into the Composio constructor:
+```typescript
+import { Composio } from '@composio/core'
+import { VercelProvider } from '@composio/vercel'
+
+const composio = new Composio({ provider: new VercelProvider() })
+```
+```python
+from composio import Composio
+from composio_langchain import LangchainProvider
+
+composio = Composio(provider=LangchainProvider())
+```
+
+---
+
+## Building Agents
+
+Use Tool Router to create isolated MCP sessions per user with scoped tool access and automatic auth management. Compatible with any AI framework.
+
+### Session Management
+- [User ID Best Practices](tr-userid-best-practices.md) — choose user IDs for security and isolation
+- [Creating Basic Sessions](tr-session-basic.md) — initialize Tool Router sessions
+- [Session Lifecycle](tr-session-lifecycle.md) — when to create vs reuse sessions
+- [Session Configuration](tr-session-config.md) — configure toolkits, tools, and filters
+- [Using Native Tools](tr-mcp-vs-native.md) — prefer native tools for performance and control
+
+### Authentication Flows
+- [Auto Authentication in Chat](tr-auth-auto.md) — enable in-chat auth flows
+- [Manual Authorization](tr-auth-manual.md) — use `session.authorize()` for explicit flows
+- [Connection Management](tr-auth-connections.md) — configure `manageConnections`, `waitForConnections`, and callback URLs
+
+### Toolkit Querying & UI Building
+- [Building Chat UIs](tr-building-chat-ui.md) — toolkit selection, connection management, and session handling
+- [Query Toolkit States](tr-toolkit-query.md) — use `session.toolkits()` to check connections and build connection UIs
+
+### Framework Integrations
+- [Framework Integration](tr-framework-integration.md) — LangChain, OpenAI Agents, general patterns
+- [Vercel AI SDK](tr-framework-ai-sdk.md) — native tools, MCP, and React
+- [Mastra](tr-framework-mastra.md) — Mastra agents with native tools and MCP
+
+### Event-Driven Agents (Triggers)
+- [Creating Triggers](triggers-create.md) — set up trigger instances for real-time events
+- [Subscribing to Events](triggers-subscribe.md) — listen to trigger events in real-time
+- [Webhook Verification](triggers-webhook.md) — verify and process incoming webhook payloads
+- [Managing Triggers](triggers-manage.md) — enable, disable, update, and list triggers
+
+---
+
+## Building Apps
+
+Direct tool execution without agent frameworks — full control over auth, execution, and resource management. If building apps with agentic abilities, make sure the auth configs match the session's auth configs.
+
+### Core Operations
+- [Fetching Tools](app-fetch-tools.md) — get tools with filters and search
+- [Direct Tool Execution](app-execute-tools.md) — execute tools manually with parameters
+- [Tool Version Management](app-tool-versions.md) — version pinning strategies for stability
+
+### Resource Management
+- [Connected Accounts CRUD](app-connected-accounts.md) — create, read, update, delete connected accounts
+- [Auth Config Management](app-auth-configs.md) — manage authentication configurations
+- [Toolkit Management](app-toolkits.md) — query toolkits, categories, and auth requirements
+- [Auth Popup UI](app-auth-popup-ui.md) — build popup-based OAuth flows
+
+### Extensibility
+- [Tool Modifiers](app-modifiers.md) — schema modification and execution hooks for logging and modifications
+
+### User Context & Multi-Tenancy
+- [User ID Patterns](app-user-context.md) — user vs organization IDs, shared vs isolated connections
+
+### Event-Driven Applications
+- [Creating Triggers](triggers-create.md) — set up trigger instances
+- [Subscribing to Events](triggers-subscribe.md) — listen to events in real-time
+- [Webhook Verification](triggers-webhook.md) — verify incoming webhooks
+- [Managing Triggers](triggers-manage.md) — enable, disable, update triggers
+
+---
+
+## Verify Tool Slugs Before Use
+
+Never guess toolkit, tool, or trigger names. Always verify:
+
+```bash
+composio search "send email"
+composio manage tools info "GMAIL_SEND_EMAIL"
+composio manage toolkits info "gmail"
+```
+
+Using incorrect slugs causes runtime errors.
+
+---
+
+
+---
+
+_This file was automatically generated from individual rule files on 2026-03-13T12:37:41.138Z_
+_To update, run: `npm run build:agents`_