Projects & files
Targets, workspaces, projects & conversations
Understand the four levels so work uses the intended computer, context and project.
What does each level control?#
| Object | Controls | Example |
|---|---|---|
| Execution target | Runtime and accessible files | Office computer, local computer, ECS cloud |
| Workspace | Conversations, projects, sources, skills and settings | Design workspace |
| Project | Conversations and assets for one body of work | Demo hotel design |
| Conversation | A specific task with continuing context | Lobby stone comparison |
| Use this order: target → workspace → project → new conversation. |
Try the structure#
- Select a design workspace on your computer and create “Demo hotel design”.
- Create separate conversations for “Stone comparison” and “Joinery reference check”. Keep each task's context focused.
- Inspect the working folder in project details before asking tools to read files.
- Before switching computers, note which computer owns the project. Select that computer and its workspace in the remote view.
Why does the same account show different content?#
The same account can discover and control registered, synchronized computers. It does not merge projects or folders with identical names across devices. A cloud conversation is separate from a local one. Reading mirrored history on a phone does not mean the source attachments are stored there.
Confirm your context#
State which project, attachments and working folder the task should use. If a path cannot be opened, check the execution target and the actual file location before investigating the model connection.
Based on MATLOOK Agent functionality, bundled help and release notes. Available controls depend on the installed version, execution target and account permissions. Versions & editorial notes ↗