Build Workspaces and Agents
Link code folders to Ansight Studio Build, manage Codex and Claude tasks, follow agent activity, send follow-ups, and include focused app evidence.
The Build workspace pane anchors agent work to a development folder. It groups tasks by codebase while keeping the selected device and live Ansight session available as context for the current chat.
Linked Workspaces
Build can:
- link a development folder without changing the source tree
- remember the selected workspace
- show the folder name and path
- open the folder from its context menu
- unlink the folder from Build without deleting it
- detect whether the workspace already includes Ansight
- start an install or migration skill when integration is missing or needs attention
The integration check is guidance, not a tool authorization. The app still decides which runtime tools it exposes through its SDK configuration and guard.
Task Discovery
Build reads tasks made available by supported local agent providers.
| Feature | Behavior |
|---|---|
| Workspace task list | Shows Codex and Claude tasks associated with the selected folder. |
| Global task search | Searches across every available Codex and Claude workspace after a workspace is selected. |
| Status and preview | Shows provider, working state, latest activity, and a compact status indicator. |
| Pinning | Pins or unpins supported tasks and sorts pinned work first. |
| Refresh | Refreshes workspace links, task lists, and global search results. |
| Open in Codex | Opens a selected Codex task in the Codex app when a compatible task URL is available. |
Starting and Continuing Work
Select New chat to start a task in the current workspace. The first message creates the provider task; later messages continue that same task.
The activity view follows:
- user and agent messages
- command execution
- CLI, dynamic, and collaboration tool calls
- file-download progress, including determinate or indeterminate progress
- task status and working state
- the latest activity while a task is still running
Build keeps the activity feed pinned to recent work and exposes a compact message composer for follow-up instructions.
Focused App Context
When a message is sent, Build can include ambient context for the current development loop:
- selected device kind, name, runtime, and identifier
- connected live Ansight session ID
- live app file snapshots explicitly attached to the chat
The focused device is included only for a booted non-macOS simulator or emulator. The session ID is included only while the selected app session is live and connected. File attachments must be added explicitly and can be removed before sending.
File Attachments
The Live Files panel can save a selected app file as an evidence snapshot and attach it to the current chat. Build shows the file name and source detail as a removable chip in the composer. After a successful send, submitted attachment chips are cleared from the composer.
See Live Files and Viewers for supported actions and formats.
Practical Workflow
- Link the source folder and select it.
- Choose an existing task or start a new one.
- Select the simulator, emulator, or live app target involved in the issue.
- Reproduce the behavior and inspect the relevant live capability.
- Add a file snapshot when the agent needs exact app-owned data.
- Send a focused instruction; Build supplies the selected runtime context with it.
Boundaries
- Linking a workspace does not grant Studio or an agent unrestricted filesystem access.
- Build does not attach every app file automatically.
- A task provider can reject task creation, continuation, pinning, or deep-link opening.
- App-owned evidence remains subject to the SDK tool guard and live connection state.