Keep control of the work

Tell teammates what you authorize, review requests that need your input, and choose carefully what you include in shared material.

State the intended action

A clear request distinguishes preparing a draft from sending it, and reviewing a file from changing it. Name the recipient, app account, repository, or destination when the action affects something outside the conversation.

Approval cards show an action that needs your response. Read the request and approve or decline it there. An approval-required activity is waiting for a decision; it is not a completed action.

Cloud coding publishes a task branch when changes are collected successfully. Requesting no pull request does not prevent branch publication. Review the cloud coding guide before launching a repository task.

Use the right input surface

Use a protected credential request for an API secret. Use computer takeover for a website login, passkey, or other step that requires your direct interaction.

Manage app accounts individually from their connection details. Disconnect the selected account when it should no longer be available.

Review what you share

A marketplace pack includes the instructions and skills shown in its preview. Read them before publication and remove information that should stay in your workspace. Anyone with a private team link can use that link.

Review saved memory when project details or preferences change. Use the available edit, forget, or undo controls for the relevant record.