Kimi Code + Notion
Kimi Code runs the task; the Notion connector supplies only the operations and resources allowed by the account you authorize. The Composer selects Kimi Code, asks for Notion access before sending, and keeps both choices in one task draft.
How the combination works
Kimi Code plans and executes. Notion supplies authorized app access.
Kimi Code supplies a repository-focused coding loop for reading large code contexts, editing files, and running validation in a cloud workspace.
Notion is a new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team.
Kimi Code
Owns the task loop, model calls, cloud computer, tool choices, progress and final result.
Notion connector
Supplies the currently exposed operations for the authorized Notion account. It does not promise every feature in the Notion product.
Permission boundary
The connected identity, granted provider scopes, organization policy, resource sharing and the task's explicit instruction all constrain what Kimi Code can do.
Setup and first task
Connect one Notion account and verify one known resource.
The Composer preselects Kimi Code with Kimi K3. Start read-only when possible, then expand to write operations only after the account and resource boundary are clear.
Open the Kimi Code Composer
The Composer above carries Kimi Code, Kimi K3, and Notion. Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.
Authorize the intended Notion account
Choose the intended workspace and review which pages the connection may access. A connected workspace does not mean every page has been shared.
Run and verify a bounded task
Ask the agent to read one explicitly shared page and turn its requirements into a checklist with a link back to the source. Do not request edits for the first access test. Compare the summary with the current Notion page. For later edits, reopen the destination page and inspect the changed blocks.
Access, cost and limits
What to verify before scaling Kimi Code + Notion
Repository work that benefits from Kimi Code's coding workflow and long-context model options.
Establish with the first run
- Kimi Code and Kimi K3 remain selected after sign-in.
- Notion shows the intended connected account before the task is sent.
- The returned data matches one known source resource, with write actions excluded until separately authorized.
Still depends on your setup
- A catalog listing does not guarantee every Notion website feature is available as an agent operation.
- OAuth scopes do not replace organization policy, resource sharing or a precise task instruction.
- Total task cost can include model tokens, active computer time, paid tools, connectors and the provider's own plan or quota.
Verification and recovery
Check Notion itself before trusting the result.
Compare the summary with the current Notion page. For later edits, reopen the destination page and inspect the changed blocks.
Connection troubleshooting
Check the workspace and whether the requested page is shared with the connection. A page URL alone does not grant access.
Writes need explicit scope
Name the target record and exact allowed change. A request to summarize, analyze or draft does not authorize sending, publishing or deleting.
Re-check current state
For decisions or follow-up writes, open the resource in Notion and check its current state. A successful earlier read may already be stale.
Common questions
Related resources
Kimi Code
Review Kimi Code's supported models, capabilities and browser Composer.
Notion connector
Review the application-specific authorization and first-task guide.
Kimi Code + Kimi K3
Review the current default agent and model combination.
Pricing
Review model, active-computer, tool and connector charges.