Overview

Tasklet is the AI command center for your team’s threads, connections, knowledge, and apps. Unlike a chatbot that just answers questions, Tasklet takes ownership of work: it sends emails, updates spreadsheets, files tickets, builds apps, and runs recurring processes across your tools. Describe the outcome in plain English, and Tasklet figures out the rest.

It connects to your whole stack: thousands of apps are one click away, plus any HTTP API or MCP server—even the private tools your company built itself. Each thread gets its own secure computer in the cloud to run code, process data, and open a browser when an app has no API. And because threads run in the cloud, they keep working when your laptop is closed—on a schedule or when events happen, like a new email or Slack message, with no one pressing go.

Best of all, Tasklet is built for teams: share connections, threads, and knowledge across the company, with credentials locked down and access set once. You get frontier models from Anthropic, OpenAI, and Google in a single plan—routed to whichever does each job best—plus granular access controls, centralized billing, and enterprise-grade security. It’s how teams scale productivity without adding headcount.

Connections

Connections are how Tasklet accesses all your apps. Tasklet has over 3,000 built-in integrations, and it can connect to any API (including private APIs) or MCP server. It can also access services via a browser (see the “Browser” section below). To connect a service just ask “Connect my Gmail” or whatever service you’d like to connect to.

How Connections Work

1. You authorize access — Tasklet opens a secure login flow. You sign in directly with the service.
2. You control permissions — After connecting, you choose which capabilities to grant. Each connection unlocks specific tools (like “send email” or “create task”). Tasklet asks permission before activating new tools.
3. The tools become available — Once authorized, Tasklet can use those tools to complete tasks on your behalf.

💡 Tip: If Tasklet says it can’t do something with a connected service, it may need additional tools activated. You can say “Show me what tools are available for [service]” to see options.

What you can connect

Here are some of the most popular built-in connections by category:

Custom APIs & Integrations

Tasklet can connect to any HTTP API or MCP server directly. Describe what you want to connect to, and Tasklet will set up a connection flow where you can securely provide your credentials.

“Connect me to our inventory API so I can monitor stock levels and alert team members when we’re running low.”

You can also connect to internal company APIs. Share instructions or reference files with Tasklet and it will learn to make requests.

Security protections

• Your credentials are encrypted and stored securely within the connections flows—Tasklet never sees your passwords
• Connections use OAuth when available (you log in directly with the service)
• You can revoke access anytime from Settings → Agent → Connections
• After approving an app connection, you control exactly what tools Tasklet can access. For example, you can grant read-only access—letting Tasklet see your data without changing it.

Automations

Automations let Tasklet run on a schedule, when emails arrive, or in response to external events.

How to create an automation

Describe what you want to happen and when:

“Send me a daily briefing every morning at 9am.”

“When I get an email with an attachment, file it in Drive.”

You can also say “create an automation for…” to be explicit.

Types of automations

💡 Tip: You can add a filter to Gmail automations to reduce the number of emails being processed and lower credit usage. For example, you can filter by attachments only, specific senders, or emails marked as important. To do this, specify the filter when creating the automation: “When I get an email with an attachment…”

To test, delete, or view details of an automation, ask in the thread or select the automation icon (⚡) in the chat toolbar.

Multiple automations per thread

A single thread can handle multiple automations. For example, an inbox assistant thread could:

• Run a daily briefing every morning
• Draft replies for incoming emails
• Star important messages automatically

Text & Email Messaging

Tasklet can send and receive messages via email or text (iMessage & RCS). When someone responds, your thread receives the reply and can take action.

Email anyone (with permission)

You can add any email address as a contact method. The recipient clicks a verification link to opt in, and then your thread can send them messages—reports, notifications, requests for approval, etc.

Text messaging

Tasklet can also send and receive text messages via iMessage and RCS. This is useful for time-sensitive alerts or when you want to interact with your thread on the go.

Two-way conversations

Recipients can reply to Tasklet’s emails or texts. Your thread receives the response and can continue the conversation or take action based on it. Recipients don’t need a Tasklet account.

How to set it up

1. Ask in any thread to add a contact method (email or phone number)
2. The recipient verifies—clicking a link for email, or sending a text for phone numbers
3. Once verified, your thread can message them anytime

Example prompts

• “Every Friday, email the sales team a summary of closed deals”
• “Text me if any emails come in from my boss”
• “Include my teammate in these reports, their email is…”

File Processing

Tasklet can transfer files between connections (Gmail, Drive, Slack, APIs, etc.), process them, and create new files.

What it can do

Combine files with automations

You can combine file processing with automations to run recurring workflows:

• Every morning, pull data from your CRM and generate a summary report.
• When receipts arrive in your inbox, extract the data and add a row to a spreadsheet.
• On a schedule, check a public dataset and alert you if anything changes.

Example prompts

• “When I get an invoice emailed to me, save it to my ‘Invoices/2026’ folder in Drive and log it in my expenses spreadsheet.”
• “Analyze this CSV and send me a summary with charts.”
• “Resize all images in this folder to thumbnails.”
• “Download all my receipts from Doordash and upload them to Drive.”

Browser

Every Tasklet thread has a built-in web browser it can use to visit and interact with any website. The thread can use it for example to access authenticated sites or fill out forms.

How to use it

Just describe what you need and Tasklet will open a browser if it helps:

Log into my Google Ads account and take a screenshot of this week’s campaign performance dashboard.

You can also say “use the browser to…” to be explicit, but usually you should let the thread choose the best approach. In many cases using a built-in integration or non-interactive web tools will be faster, more reliable, and use fewer credits.

What it can do

• Navigate complex pages, enter text, interact with buttons and other elements
• Fill out forms and click through multi-step flows
• Extract data from pages (tables, listings, article text)
• Upload and download files
• Scroll long pages and interact with dynamic content
• Hand off sign-in or CAPTCHA steps to you when a site requires them

Logins and CAPTCHAs

Tasklet will never ask you for your password. When a site needs you to sign in, or a CAPTCHA appears, the thread navigates to the login page and shows you a live browser preview in the conversation. You take over in the preview—enter your credentials or solve the challenge directly—and then hand control back. The thread continues from there.

Saved logins and cookies

The browser keeps a persistent profile for each thread. Once you’ve signed into a site through the browser preview, the thread stays signed in for future tasks—you don’t have to re-enter your credentials each time. Cookies, site preferences, and any data the site stored locally carry over the same way.

If a thread goes unused for over 30 days, the browser’s saved state may be cleared and you’ll need to sign in again the next time the thread visits that site.

Example prompts

• “Log into my company’s Workday portal and submit my timesheet for this week.”
• “Log into my Google Ads account and take a screenshot of this week’s campaign performance dashboard.”
• “Log into Gusto and download the last 3 payroll summary PDFs.”
• “Go to the DMV appointment scheduler, find the earliest available slot in San Jose, and book it for me.”
• “Search Google Flights from SFO to NYC for next Friday, apply ‘nonstop only,’ sort by price, and screenshot the top results.”
• “Log into my accountant’s client portal and upload these three PDF documents.”
• “Go to DoorDash and re-order my last Thai food order.”

Instant Apps

Instant apps are lightweight, interactive web apps that run inside Tasklet’s preview panel. Use them when you need an interface to click through, filter, sort, or enter data while continuing your conversation.

Instant apps are a good fit for dashboards you want to drill into, trackers or lists with inline edits, interactive calculators or forms, kanban-style workflows, and plenty more.

What makes instant apps powerful:

• Live data — Apps can use your connected services to show current data, not mockups.
• Two-way sync — Changes you make in the app write back to your tools.
• Feedback loop — Actions you take in the app flow back to the thread, so it can respond to what you clicked or edited.
• Saved — Apps are saved to the thread’s filesystem, so you can revisit or update them later.

Example prompts:

• “Build a dashboard showing my open Linear issues grouped by priority.”
• “Create a kanban board for the projects in my Notion database.”
• “Make an interactive chart of monthly revenue from the sales spreadsheet.”

Organizations

An organization is your team’s home in Tasklet. It groups your members, your agents, and your billing in one place. Everyone you work with joins the same organization, and from there you decide who can do what.

How Tasklet is organized

• Organization — your company’s account. Holds your members, agents, and billing.
• Members — the people in your organization, each with a role: Owner, Admin, or Member.
• Agents — where threads, connections, and knowledge live. Access is determined by the agent’s members.

In short: an organization contains members and agents; an agent is where your team actually does the work.

Roles

Every member of an organization has one of three roles:

Inviting people

People join an organization by invitation. By default, any member can invite new people; an admin can lock this down to admins only from Settings → Organization → Members. When you invite someone, you choose the role they join with (Member or Admin), and you can change it later from the same page.

Agents

An agent is where your threads, connections, and knowledge live. Every agent starts with only its creator as a member, so its contents are initially accessible only to them. You can add other organization members during creation or at any time later.

Any member of your organization can create an agent by selecting New agent in the agent rail.

Sharing an agent

When you add someone to an agent, they get access to everything in it:

• Threads — every thread in an agent is automatically available to all of its members. There’s no separate “share” step: start a thread in an agent and your teammates can use it, pick up where it left off, and see its work.
• Connections — connections added in an agent go into a shared pool. Any member’s threads can use them, so you only connect a service like Slack or a shared inbox once for the whole team.
• Knowledge, instructions, and skills — the agent-wide guidance covered in the next section applies to every thread and every member here.

💡 Tip: Because connections are pooled, a teammate’s thread can act through a service you connected. Only add members to an agent if you’re comfortable letting them use its connections. Keep personal accounts in an agent where you are the only member.

Managing members

Members are managed from Settings → Agent → Members. You can add anyone who’s already in your organization, and remove them when they no longer need access.

• Agent members can add and remove other members, start threads, rename the agent, and archive it.
• Organization owners and admins can manage any agent in the organization, plus unarchive agents and set per-agent usage limits.

Knowledge

Knowledge is the custom instructions, files, and Skills your threads use to work the way you want. Each agent has its own Knowledge, managed from Settings → Agent → Knowledge.

Tasklet has two Knowledge layers:

• Agent Knowledge contains custom instructions, files, and Skills for threads in that agent.
• Organization Knowledge contains files and Skills available across every agent in the organization.

Use Agent Knowledge for agent-specific instructions and references. Use Organization Knowledge for company-wide information, such as definitions, policies, and brand guidance.

Threads can read both layers. They can request edit access to Agent Knowledge and make changes when you approve it. Organization Knowledge can be edited only by Organization Owners and Admins. Members and threads have read-only access.

Custom Instructions

Custom instructions are house rules every thread in the agent follows—tone of voice, formatting, things to always or never do, and basic context about your company. Set them once instead of repeating yourself in every conversation.

Examples of useful instructions:

• “Always write in British English and use our brand name ‘Acme’ (never ‘ACME’).”
• “Our fiscal year starts in February—assume that for any reporting.”

💡 Tip: Instructions are capped at 10,000 characters—keep them focused on rules and context, and put longer reference material in Agent Files instead.

Agent Files

Agent files are a shared library your threads can read—docs, policies, data, templates, anything you want them to know. Create files, folders, or skills, upload your own, edit text and Markdown files in the browser, and download files or whole folders.

Threads pull from agent files automatically when it’s relevant:

• “What’s our refund policy?” → the thread reads it from the policy doc you uploaded.
• “Draft a proposal using our standard template.” → the thread starts from the template in your files.

Skills

Skills are reusable, step-by-step playbooks for tasks your threads do over and over—a packaged procedure any thread in the agent can run consistently.

Each skill has a name, a short description of when to use it, and its instructions (plus any supporting files). Threads see all available skills and reach for the right one when a task matches.

You create and manage skills from the same Knowledge area:

• Pre-built skills — install ready-made skills from the gallery with one click.
• Custom skills — create your own: give it a name, a brief description, and the instructions the thread should follow.

Examples of skills you might create:

• A weekly report skill that defines exactly how your reports should be structured and sourced.
• A support triage skill that encodes how to categorize and route incoming tickets.

💡 Tip: Not sure whether to use instructions, files, or a skill? Use instructions for always-on rules, files for reference material, and a skill for a repeatable procedure with clear steps.

Advanced Capabilities

Filesystem

Every Tasklet thread has a persistent filesystem that survives across sessions. Rather than holding everything in its context window, your thread writes to disk. This means it can work with large files, build up results over time, and pick up where it left off.

What lives there:

💡 Tip: The filesystem, skills, and memory described in this section are private to a single thread. For instructions, files, and skills shared across every thread in an agent, see the Knowledge section above (Custom Instructions, Agent Files, and Skills).

Working with connections:

Tasklet can download files from connections to the filesystem, and upload files from the filesystem to connections.

Example prompts:

• “Save a summary of this research to refer back to later.”
• “Show me the files you’ve created for this project.”
• “Keep a running log of all the leads you find.”

Media

Tasklet can create images and short videos directly in the app. It can also transcribe audio and video files so you can summarize, analyze, or use their contents in other work.

What it can do

Example prompts

• “Create a product image with a transparent background.”
• “Generate a short launch video for this new feature.”
• “Transcribe this customer call and pull out the main requests.”

Sandbox (Code Execution)

Every Tasklet thread has a Linux sandbox for running code and processing files.

Pre-installed tools:

• ffmpeg — audio and video processing
• ImageMagick — image manipulation and conversion
• Pandoc — document format conversion
• curl, jq — web requests and JSON processing
• Python 3.12 with access to any package (pandas, numpy, matplotlib, etc.)

Installing packages:

The sandbox can install any additional package on demand. If a task requires a specific library or tool, Tasklet installs it and proceeds.

Filesystem access:

Code running in the sandbox can read and write to the thread’s filesystem. Scripts can be saved and rerun later, or process files that have accumulated over multiple sessions.

Example prompts:

• “Analyze this 10,000-row CSV and give me summary statistics with visualizations.”
• “Convert all these Word docs to PDFs.”
• “Write a script that checks this API every hour and alerts me if the price drops.”

Memory (SQL Database)

Every thread has its own persistent SQL database to store and retrieve data across sessions. This is how your thread “remembers” things over time.

What it’s for:

• Tracking progress on recurring tasks
• Avoiding duplicate work (“have I already processed this?”)
• Storing information that builds up over time
• Keeping configuration that changes between runs

If you want your thread to remember something specific, you can tell it explicitly:

• “Store all the contacts you find in your database so you don’t look them up again.”
• “Remember everything we learn about Acme Corp in your database.”
• “Track all the vendors we’ve evaluated, their pricing, and our notes in the database.”

Subagents

For complex tasks, Tasklet spins up focused subagents to handle specific parts of the work, like mini-workers with clear instructions for their job.

How they work:

Subagents are each focused on a specific task. When finished, they report back the result, keeping work organized and costs down.

Why it matters:

• Breaks big tasks into smaller, manageable steps
• Keeps costs down: each subagent works with only what it needs
• Processes long lists without losing track (e.g., reviewing 50 resumes one by one)
• Handles heavy lifting like web scraping or document analysis in isolation

Tasklet often creates subagents automatically, but you can request them explicitly:

• “Create a subagent to research each competitor, then compile the results into one report.”
• “Use a subagent to review each resume in this folder and score it against our job criteria.”
• “For each lead in this list, have a subagent research the company and draft a personalized outreach email.”

Webhooks (External API)

Tasklet can receive data from external services through webhooks. Each webhook provides an API endpoint that starts an AI-powered workflow.

How to set it up:

“Set up a webhook automation that runs when I get a new order from my Shopify store.”

Tasklet creates a unique URL. Point your external service at that URL, and when it sends data, Tasklet wakes up and processes it.

Examples:

• Stripe sends a webhook when a payment succeeds → Tasklet updates your CRM and sends a welcome email
• GitHub sends a webhook on new issues → Tasklet triages and labels them
• Your app sends a webhook when users sign up → Tasklet enriches profiles and notifies sales
• Meeting transcription service sends a webhook → Tasklet creates tasks and emails a recap

Thread-to-thread communication:

Webhooks also enable threads to talk to each other. One thread can make a Direct API call to another thread’s webhook URL to start it. This is useful for coordinating work between specialized threads.