m365-copilot-cdp

Topics in the source

• Microsoft 365 Copilot desktop CDP
• Outcome
• Authority
• Prerequisites and commands
• Requests
• Completion and handoff
• Basis

Use the existing desktop session and exact requested mode/model to obtain the requested conversation state or a completed new assistant reply. The next consumer receives JSON containing the actual rendered result and its turn identity. A Send click, an empty composer, an old reply, or stable text is not completion evidence. Chat and Code have separate model/completion contracts. Code needs its native host, not a generic browser facade. Read the UI contract when modes, models, selectors, or completion evidence differ. Inspect/read only what the user requested. Sending a prompt requires explicit authorization for its exact purpose; app access alone is not send authority. Keep existing drafts. The adapter rejects composing or changing modes with a nonempty draft. A pre-existing menu must be closed manually before model discovery/selection. Code can modify files, run commands, install packages, and connect to services. A prompt authorization does not authorize those actions, project creation, onboarding acceptance, tool approvals, or persistent permission changes. After any error from a Send attempt, treat the result as uncertain. Read the conversation and ask the user to reconcile it;

This is an excerpt. Refer to the complete source and its current requirements.