← All agent and harness briefs
Agent runtimeagenticopsresearchgtmdocumentedunattended capable

Operational brief

Lindy

A hosted personal and Slack teammate for connected tools, meetings and optional routines, with write guardrails limited to shared Slack threads.

No product visual on file

Choose it when

You can configure integration-wide write rules for shared Slack work and separately review private-surface actions, connected-account authority and routine delivery.

Skip it when

You need to operate the runtime yourself, refuse per-user usage credits, or cannot use a hosted system with connected business data.

01 / Classification

Autonomy evidence

This is our classification, not a vendor badge. The record says what the product normally does. The gaps stay visible.

How we classify it
Tool use + multi-step plans, still human-gated per session.
Runs unattended
Yes — that capability is documented in this brief.
Trigger
Normal use is a user task in chat, DM or a channel mention. Optional routines run on schedules or events; personal routines are user-owned and workspace routines require admin setup/management.
State
Versioned personal, team and system files provide context across tasks. Team files are readable by members but editable by owners/admins; deletion keeps older versions. Personal context isn't automatically team context.
Tools
Can act through connected apps, browser/API work and MCP. Always allow, Require approval and Don't offer apply integration-wide to writes in shared Slack threads, not per-account and not private chat/text surfaces.
Human control
The requester can approve their own Slack write; owners/admins can also approve. Users/admins must review and toggle their routines. Dry run suppresses writes but uses real reads and can't validate delivery. Personal script conversion switches the routine off for review/testing/re-enabling; scripts lack connected-account credentials, and a crash wakes Lindy for repair, not a guaranteed recovery outcome.

02 / Operations

Control reality

Useful agents eventually touch something real. This is the operational picture we have, not a promise hidden in a sales page.

Where it runs
Hosted service accessed through web/chat surfaces; browser/computer use is documented, not evidence of self-hosting or unrestricted availability on every plan.
Data boundary
Personal connections/files and shared workspace connections/files have different scopes. Public-channel capabilities are narrower than the private toolset. Version history survives file deletion; no independently verified retention or no-training guarantee is asserted here.
Identity & permissions
A shared connection acts with the connected account's permissions, not each requester's personal authority. Guardrails cover all accounts under an integration. Requester self-approval is allowed; Always allow can change a member's scope or the whole workspace depending on who clicks.
What it can write
Email, calendar and connected-tool actions; approval depends on surface and guardrail setting · Documents, posts and business records · Scheduled or event-triggered routine outputs · Versioned personal/team memory files
Surfaces
Web chat and Slack · Gmail and calendar · Meet, Zoom, and Teams meeting participation · iMessage and SMS · Browser/computer-use capability, plan and setup dependent · MCP
Export / lock-in
Meetings expose copy/download/share controls and memory files expose Raw/History views. A complete agent/workspace migration export isn't established by these documents.

03 / Receipts

Evidence ledger

Here is what this brief is built on. “Documented” means we found a source. “Tested” means this desk actually ran it. Those are different things.

Evidence status
documented
Source set
10 primary sources
Evidence review
2026-10-15

Sources on file

Corrections

  • 2026-10-15 · Removed blanket external-action approval wording: detailed docs limit integration write guardrails to shared Slack threads and permit self-approval/Always allow. Primary facet is task-led with optional routines. Changed Freemium to Paid with trial/billing conflict disclosed; distinguished Teams chat from meeting participation, versioned memory and dry-run/script limits; not runtime-tested.

Desk notes

What we found

Useful context, not a substitute for the source record above. This is not a desk test unless the evidence status says tested.

Pick it for connected task and routine work after checking surface-specific controls; skip it if blanket approval or durable free access is essential.

Guardrails
Shared Slack writes only; no per-account rule
Identity
Shared connection uses its connected account
Automation
Schedules/events; dry runs don't prove delivery
Access
Paid seats/credits; limited free trial

What the vendor says

Precise integration docs contradict universal approval language in pricing FAQs. Teams chat is coming soon, while Teams meeting recording remains documented. Free-credit and direct-signup wording also needs checking; not runtime-tested.

Sources fetched 2026-10-15

04 / Change log

Related coverage

The brief tells you what the product is. Payloads track the changes that may alter the decision.

No linked change coverage on file yet.