Profound wants to connect to Slack
Agent plan + activity
An agent-plan surface embedded in a chat thread. Each section — the plan-update note, the plan header, the running step + activity log, and inline connection approvals — is its own component; AgentPlanActivity threads them together with a connecting line.
Included in the single kansho full pack. Components are not offered as separate installs.
Full plan — threaded
Disclosures are live; plan, item, and connection actions are preview callbacksUpdated Agent Plan
Done, I updated the title from Best to Top.
Changed “Best” to “Top”
Blog post update
Set visibility alertSteps 4 of 62m 19s
Read/docs/model-coverage
1.2s1,420 words · 6 sections
Fetch competitor citations (last 7d)
3.4sUpdate matrix with Gemini 2.5, Llama 4
8.1sDraft/briefs/tool-use-benchmarks
1m 14sSet visibility alert (< 14% · 2 checks)
Post summary to #brand-team
Sections, on their own
Each block is reusable; the displayed actions are static-preview callbacksPlanUpdateNote
Updated Agent Plan
Done, I updated the title from Best to Top.
Changed “Best” to “Top”
PlanHeader
Blog post update
PlanRunningStep
Set visibility alertSteps 4 of 62m 19s
Read/docs/model-coverage
1.2s1,420 words · 6 sections
Fetch competitor citations (last 7d)
3.4sUpdate matrix with Gemini 2.5, Llama 4
8.1sDraft/briefs/tool-use-benchmarks
1m 14sSet visibility alert (< 14% · 2 checks)
Post summary to #brand-team
Connection (SoftwareConnectCard)
Profound wants to connect to Slack
Plan header — states
View plan uses a static-preview callbackBlog post update
Refactor auth module
Weekly digest (no actions)
Running step — activity open vs collapsed
Run integration testsSteps 3 of 547s
Read/lib/auth.ts
900msExtract token helper
12sRun integration tests
Update docs
Compose emailSteps 2 of 38.0s
Threaded — no update note or connection
Composer with just header + running step; plan actions are static-preview callbacksRefactor auth module
Run integration testsSteps 3 of 547s
Read/lib/auth.ts
900msExtract token helper
12sRun integration tests
Update docs
Component documentation
Agent Plan Activity
components/agent/agent-plan-activity.tsxPurpose
Tracks an executing plan as an update note, plan header, running step, activity list, and optional connection requests.
Appropriate use
Use inside an agent thread when the operator needs progress and intervention context without opening a separate run view.
Example
components/agent/agent-plan-activity.tsx has a representative live example in the "Full plan — threaded" section on /components/agent-plan-activity.
States
Covers triggered or untriggered headers, collapsed or open activity, every shared status, optional update notes, and connection cards.
API and props
Exports AgentPlanActivity, PlanHeader, PlanUpdateNote, and PlanRunningStep; props cover plan text, step position, elapsedMs, activity, connections, disclosure defaults, and callbacks.
Dependencies
Direct imports are React, Lucide icons, Button, Tag, StatusGlyph, SoftwareConnectCard, status types, duration formatting, and cn.
Accessibility
Activity disclosure buttons expose expanded and controls state; revert has an accessible name, while status meaning is repeated in text or shared glyph labels.
Limitations
The host owns plan execution, elapsed-time updates, action results, and connection resolution; animate-enter-up is presentation only.
Source
Source: components/agent/agent-plan-activity.tsx.
Full pack
components/agent/agent-plan-activity.tsx is documented at /components/agent-plan-activity and installs only through the single Kansho full pack; no individual component install is offered.