Chief of Staff
Every Aide user gets a Chief of Staff.
One standing conversation — not another agent to configure. It gets to know you, never resets, and only two things come back: finished work and decisions that need your sign-off.
One standing conversation, pinned to the top of your sidebar — not another agent to configure. Your Chief of Staff opens by getting to know you, never resets, and learns your priorities, preferences, and ongoing work through Aide’s memory. It breaks jobs down, runs them in the background, and follows through — and only two things come back to you: finished work and decisions that need your sign-off.
Delegate real work
Hand off a job and it runs in the background as a real Aide chat with your full context, memory, and tool permissions. Open it mid-run to watch it work, or read the result later — every delegated chat is on the record.
Plans you can read
Work gets planned in dated, plain-language documents in your vault, and background runs write their outcomes back — so the plan, not a chat scroll, is the durable record.
Recurring work in plain language
Say “review my plans every morning at 8” and it becomes a real schedule — pause, resume, or delete it whenever you like.
Sign-offs on your terms
Anything gated on you — send, publish, proceed — becomes an approval card that waits, even while you’re away. Approve or reject with a note; approved actions execute exactly as approved, and the work that was waiting resumes automatically.
When delegated work finishes — or gets stuck — a short, clearly labeled update posts to your main chat and the plan is brought up to date. One Command Center panel keeps pending approvals, schedules, and background runs in view with live status, and finished deliverables land in your vault.
Every Aide user gets a Chief of Staff.