Installed lists the apps you already have, including disabled apps. Discover lists apps you can add. Search works within the selected view; Templates contains starting tasks, including Website QA without creating an Agent Team.

• Open an installed app, or choose Install and open for a new one. Disabled apps offer Enable and open.
• The three-dot Manage app menu contains pinning, disabling, removal, and settings when available. On a phone, Back to apps restores your selected list item and search.
• Access and privacy expands the app's supported operations, where it runs, and connection requirements. Installation alone does not connect an account or prove Browser or Computer readiness; setup is checked when the app opens.

Open Apps in the Thread, choose Slack, GitHub, or Jira, and expand a supported capability. Use in chat prepares a request for you to review and send. Use in a team remains available for a reusable, manually designed workflow. Installing an app does not connect an account or grant permission to change anything.

1. 1Ask Browser to inspect one website and summarize the findings. Complete any access or website sign-in step before expecting a result.
2. 2After the inspection completes with evidence, ask Send these findings to Slack, or Create a GitHub issue from these findings.
3. 3Connect the missing account and choose the destination. For a new GitHub issue, choose a repository in the Thread. Search the loaded choices or use Load more; only accessible repositories with issues enabled are offered. You can also name an exact owner/repository in your request.
4. 4Select Review issue, then review the exact repository, title and full description before approving. The repository choice alone does not create an issue.
5. 5Look for the completed task and provider receipt. An approval preview is not a sent message or a created issue.

Slack and direct GitHub or Jira result actions show the exact destination and entire outgoing message, including the private Thread link. Google Workspace and Microsoft 365 result actions also show the full draft, document text, spreadsheet row or Teams message before approval. A new GitHub issue targets a repository, while a comment targets an existing issue. Check all outgoing content before approving.

1. 1For a pending Slack delivery, select Edit to change its message or choose another accessible channel in the same Slack workspace.
2. 2Select Review changes to save the updated full preview. This replaces the old approval without sending anything. Approve and send remains a separate step.
3. 3If saving fails, your draft stays in the editor. Retry the same changes, or select Check latest review if another tab has changed the task. A completed or potentially attempted delivery cannot be edited into a new send.
4. 4A scheduled report keeps its reviewed channel. Editing its message changes only that report, not the routine or Room defaults.

• If a review expires or an older review lacks the complete preview, choose Review again in the same task. Your original result and destination remain saved. Refreshing only prepares a new review; approve it separately to perform the action. The replaced review can no longer authorize a change.
• If a refresh times out, use Review again on that task. It checks the same saved action instead of rerunning the inspection or sending a message. A changed source or destination needs a new exact review and cannot inherit the previous approval.
• You can stop a pending action without deleting the inspection findings.
• If delivery has an unknown outcome, check the destination before trying again. A lost response is not proof that the provider did nothing. Review renewal is unavailable for an action that may already have been attempted.
• Hosted Browser and Computer access are separate from connecting Slack or GitHub. An installed app is not proof that its hosted runtime is ready.
• The app header keeps Back to Thread available. On phones, Apps switches apps; the composer options control reveals model selection, attachments, and shortcuts.

Use delegated sign-in for GitHub, Slack, Jira, Linear, Notion, Figma, GitLab, Bitbucket, and Vercel when available. Codelit receives scoped tokens and shows the connected identity so the user knows which account a team will use.

Select an Agent card, choose its module and provider-specific role, then choose the connected account, resource, and bounded behavior. Codelit offers the repositories, projects, pages, teams, files, or channels that account can use. Use Test read for a connected app or Check setup for a native provider operation before Live run; the same choice becomes the default in the run brief.

• Slack offers the connected bot and only channels it has joined and can read. Invite the bot to another channel, then use Refresh connected resources.
• GitHub, Jira, Linear, and Vercel actions populate issue, branch, assignee, transition, state, and deployment choices when the provider supplies them. Microsoft Teams operations populate the exact OAuth-scoped Team and channel.
• If the provider no longer returns a saved resource, Codelit marks it Saved unavailable and blocks the design-time check until you deliberately choose a replacement or reconnect. It never falls back to the first result.
• Resource IDs come from provider discovery and are never pasted into the common setup path.
• Optional action tuning stays under Optional action fields; credentials remain in the encrypted connection, not workflow JSON.

Start a connection from the selected Agent Team capability or from Settings. After the provider finishes, Codelit returns to the same route, preserves project context, and reopens the capability or Settings tab that requested the connection. A success message names the connected account, while a failed or cancelled connection returns to the same setup surface with the workflow unchanged.

Use native app capabilities for bounded reads and actions. Choose the app connection and exact capability on the responsible Agent card, then select Check setup to verify the saved credential, exact grant, required fields, and any discovered destination. The check uses a bounded no-write readiness probe and never sends the configured action. Google Workspace and Microsoft 365 use delegated sign-in; support, CRM, revenue, observability, and data apps use encrypted credentials when delegated access is unavailable.

Choose one Gmail, Calendar, Drive, Docs, Sheets, Outlook, Teams, OneDrive, or SharePoint capability, then continue on the provider's sign-in page. Codelit requests basic identity plus only that operation's delegated permission. Use Agent Team channel requests the Team, channel, sender-verification, message-read, and receipt-only reply permissions together so Trigger Hub can offer a real Team and channel picker. Use Agent Team inbox pairs bounded Gmail or Outlook read permission with send permission so Codelit can answer only through the original provider thread.

1. 1Select App capability on an Agent card, or open Settings > Apps > Connect more apps.
2. 2Choose the exact read or approval-gated action the team needs and continue with Google or Microsoft.
3. 3Review the consent screen. After approval, Codelit returns to the same card and marks only that capability ready.
4. 4Choose any discovered Team or channel, then select Check setup. A green result confirms readiness without sending a message, creating an event, or changing app data.

Access and refresh tokens are encrypted in the hosted vault and never enter workflow JSON, browser storage, analytics, or public receipts. Codelit refreshes an expiring token immediately before a run, stores rotated Microsoft refresh tokens, and preserves Google's existing refresh token during incremental consent.

• A revoked or expired authorization blocks the account and asks for reconnect.
• Reconnect must return the same provider identity; a different identity is added separately.
• Disconnect removes the local encrypted account and asks Google to revoke the delegated grant when supported.
• Temporary pasted access tokens remain under Advanced for migration and providers without a native OAuth setup.

Agent Team apps currently cover Google Workspace, Microsoft 365, Zendesk, Intercom, Stripe, Shopify, HubSpot, Salesforce, Sentry, PostHog, Datadog, PagerDuty, and Supabase. Each app exposes a small typed read and write surface rather than unrestricted API access.

• Work: Google Workspace and Microsoft 365.
• Support: Zendesk, Intercom, Stripe, and Shopify.
• Revenue: HubSpot and Salesforce.
• Engineering and data: Sentry, PostHog, Datadog, PagerDuty, and Supabase.

Connecting an app makes it available; adding its tool to an Agent Team card gives that responsibility permission to use it. Pick its exact resource and use Test read or Check setup in the card inspector. The run validator blocks design-only tools and missing credentials before Live run.

• Prefer a native action for reliable reads and writes.
• Use custom actions for an API Codelit does not yet model.
• Use Browser Operator when no suitable API exists.