Shared features
Memory, agents, skills, and settings across Chat, Code, and Files.
What is shared
Chat and Code use some of the same concepts and controls. Their storage, available tools, and execution environments differ. A shared agent profile or installed plugin does not make a local Code project an account-backed Chat project.
| Feature | Chat | Code | Files |
|---|---|---|---|
| Memory | Account and project facts; optional conversation recall | Task and runtime context; optional linked Chat recall. Code memory explains the differences | Project documents can provide context to Chat; the library is not a separate memory editor |
| Agents | Reusable assistants and their home conversations | Shared profiles used for local delegation when signed in and supported; Code agents run within task permissions | No independent agent execution surface |
| Skills and plugins | Installed tools enabled for Chat | Separate Code enablement, local installation, and runtime support | No independent plugin execution surface |
| Schedules | Account-backed chat runs | Scheduled Code tasks run on the selected desktop | Files can be inputs or outputs; schedules run in Chat or Code |
| Speech | Dictation and read aloud where supported | Transcript read aloud uses the account speech service when available | Saved Chat audio can appear in the generated library |
| Appearance | Shared application appearance | Same device-level appearance | Same device-level appearance |
Where each feature runs
PC includes Chat, local Code, and Files. Web provides account-backed Chat and Files. Mobile provides account-backed features and a separate Remote connection to a paired computer. Remote actions run on that computer; opening a Code task on a phone does not install its runtime or copy its repository.
Start with a shared guide for the concept, then use the Code-specific guide for local behavior. AI Integrator PC, Mobile, and Web describe each application.
Keep projects explicit
A Chat project groups account-backed conversations, instructions, and documents. A Code project identifies a local folder or repository. Matching names do not link them. Where linked memory is available, the user selects the Chat project explicitly. Privacy boundaries explains what stays local and what uses an account service.