“What does next week look like, and which plans are still open?”
Your home, in the conversation.
Connect Kintilla to Claude, Codex, Gemini — or any MCP-ready agent — then ask naturally. Read the week, add or edit plans, and keep the right home in context.
Sign in with Kintilla, approve your agent, and you’re connected.
Say the whole thing.
Your agent can read Kintilla, make a few related changes, and bring back one calm answer.
“Add trash every Tuesday, alternating Maya and Dev, starting next week.”
“Take down Friday’s note and archive the old one-off plans.”
Name the home once. Keep talking.
Each agent can keep a default home and active board, then you speak normally. A home or board named in a request always wins; if the choice is genuinely ambiguous, your agent asks once.
A real hand on the week.
The agent works inside the same homes, roles, and plan limits as the person who connected it.
See
Read teams, boards, walls, people, plans, and jots. Ask for one day or the whole week.
Plan
Add tasks, events, and fridge notes — including recurring plans, times, and assignments.
Change
Edit, claim, complete, reopen, skip one occurrence, or move a plan to another active board.
Let go
Archive plans, take down jots, or revoke a wall. Broad actions are named and confirmed first.
Let the routine become a routine.
If your agent supports saved or scheduled work, Kintilla can be the safe pair of hands at the end.
Scheduling and triggers live in your agent. Kintilla supplies the permission-checked reads and writes.
One connection. Then just ask.
Every call runs as you, inside the teams your Kintilla membership can reach. No shared API key, no repeating your whole setup, and nothing crosses into another home.