Generated artifacts
Copilot creates artifacts when you ask for something with structure. A report. A comparison. A parsed output. A diagram. They’re saved with the conversation that produced them and indexed so you can find them later by text, by kind, or by the question you were asking at the time. The kinds of artifacts you’ll see:- Markdown reports (rendered with tables, code blocks, and Mermaid diagrams).
- Data tables (sortable, searchable, CSV exportable).
- Code and config snippets (Monaco editor, syntax-highlighted).
- Dashboards (live metrics and charts).
- Diagrams (editable, see network diagrams).
- Diff views (before/after configs with accept/reject actions).
The Files view
Open Files from the activity bar when you know something exists but do not remember which conversation produced it. The sidebar is organized around generated artifacts, archived items, and host files. The controls at the top let you search generated artifacts, filter the list, sort by recent activity, create a new item, create a folder, or collapse the tree. Use the generated-artifact search when you remember the content. Use filters when you remember the shape: report, table, diagram, diff, code, dashboard. Use recent sort when you are continuing work from the same day. Host files are selected by host. Choose a host first, then browse files that Studio can reach through an active or configured session.Remote files over SFTP
When an SSH session is open, you can browse, read, and edit files on the remote host. Studio opens the file in the same editor you use for local code. Save writes the change back over the same session you already have open, so there’s nothing extra to configure.| Action | How |
|---|---|
| Browse | Open the SFTP panel from an active SSH session. |
| Read | Double-click a file to open in a tab. |
| Edit and save | Make changes; Mod+S writes back. |
| Upload and download | Drag files between local and remote panes. |
| Permissions | Right-click → Properties to change mode, owner, or group. |
When to create a file yourself
Use Create in Files for notes, checklists, structured reports, or scratch artifacts you want to keep with the workspace even if Copilot did not generate them. Create a folder when a maintenance window, customer, lab, or project needs a shared place for related output. Files you create manually are still part of the workspace story: they can be opened as tabs, referenced in Copilot, shared with the team when appropriate, and found later through search.Finding things
Everything in Files is indexed for search.Mod+K searches by name, content, and the conversation the artifact came from — so “BGP flap” will surface the report you wrote during the incident even if you don’t remember what you named it. Artifacts also filter by kind, which is the fastest way to narrow down when you know you’re looking for a table or a diagram specifically.
Archived files stay out of the primary working list without disappearing from the workspace. Archive old reports and one-off scratch notes when they are no longer operationally current but may still be useful as history.
Export and cleanup
Artifacts export in a format that matches their kind. Tables give you CSV. Diagrams give you SVG or PNG. Markdown reports give you.md. Code gives you the file extension appropriate to the language. The export action sits on the artifact itself, next to the open and delete controls.
Deleting an artifact clears it from the organization if it was synced. Artifacts attached to a conversation follow the conversation — if you keep the chat, the artifacts stay with it; if you clear the chat, they go too.
Related
AI Copilot
Copilot produces most of what lands in Files. Attach the right context and it’ll generate the right artifact.
Terminal
Remote files appear in Files once an SSH session is open.