Overview
A broad ClickUp surface for agents: spaces, folders, lists, tasks, custom fields, goals, and time tracking, with every write gated behind approval.
What Modus reads
- 1Workspace
- 2Space
- 2Folder
- 3List
- 4Task
You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.
2context types mined
4agent tool groups
1connection method
3security controls
Context types
Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.
Workspace context
Spaces, folders, and lists read live through the connection.
Task context
Tasks, statuses, assignees, custom fields, and comments.
Example context item
clickup_task_contextAcme›Data Platform›Q3 Roadmap›Metric layer migration
- Status
- In Progress
- Custom fields
- Impact: High · Team: Analytics Eng
- Due
- 2026-09-30
Common use cases
- 01
Give a delivery agent an accurate read of what is actually in flight.
- 02
Create follow-up tasks from a meeting summary, with a human confirming each one.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
OAuth (managed)
Managed ClickUp OAuth into your workspace.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Scoped selection
You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.
Write approval
Actions that change state in the source system are marked as writes and require an explicit human confirmation before they run.
Group access by sensitivity
Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.