Kimi Code + Bitbucket
Kimi Code runs the task; the Bitbucket connector supplies only the operations and resources allowed by the account you authorize. The Composer selects Kimi Code, asks for Bitbucket access before sending, and keeps both choices in one task draft.
How the combination works
Kimi Code plans and executes. Bitbucket 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.
Bitbucket Cloud is a Git-based code and CI/CD tool optimized for teams using Jira.
Kimi Code
Owns the task loop, model calls, cloud computer, tool choices, progress and final result.
Bitbucket connector
Supplies the currently exposed operations for the authorized Bitbucket account. It does not promise every feature in the Bitbucket 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 Bitbucket 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 Bitbucket. Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.
Authorize the intended Bitbucket account
Review the Bitbucket account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.
Run and verify a bounded task
Name one Bitbucket resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission. Open the same resource in Bitbucket and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Access, cost and limits
What to verify before scaling Kimi Code + Bitbucket
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.
- Bitbucket 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 Bitbucket 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 Bitbucket itself before trusting the result.
Open the same resource in Bitbucket and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Connection troubleshooting
If Bitbucket access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
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 Bitbucket 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.
Bitbucket 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.