Files and artifacts

The Files view is the durable entry point for work created or opened in Studio. It brings together generated artifacts, saved dashboard apps, session replays, user-created documents, and files reached through a host. Recent generated work persists beyond the chat that created it. Studio also records durable work products in organization memory so a later conversation can find and continue the right app or artifact without relying on the old transcript alone.

​

Artifact types

Copilot can create structured work such as:

• Markdown reports with tables, code, and Mermaid diagrams.
• Data tables with sorting, filtering, selection, and export.
• Code, configuration, and text in an editor.
• Before-and-after diffs.
• Network diagrams.
• Saved dashboards and sandboxed dashboard apps.
• Status cards, forms, charts, and other generated interaction surfaces.

Use a dashboard for live, refreshable operational state. Use a report or table for a point-in-time result. Use a procedure for steps the team will run again.

​

Find generated work

Open Files from the fixed sidebar. Recent artifacts appear directly in the Files surface and unified search. Search by title, content, kind, or related operational term. When you ask Copilot to continue an app or artifact from an earlier chat, Studio can use its organization work-product record to recover the locator, workspace, source host, revision, and last-known state.

​

Work with generated artifacts

Export a report as PDF when it needs to leave Studio. Export structured table data as CSV when another system will process it.

​

Dashboard apps

Generated dashboard apps are saved as immutable revisions. An accepted improvement creates a new revision rather than mutating the old source in place. Open app settings to review the current revision, requested capability grants, and permitted resource origins. See Dashboards and generated apps before granting an app external access.

​

Session replays

Terminal session recordings appear as private replay files. Open a replay from Files to review the recorded output and timeline. A replay is evidence of what Studio captured, but does not prove the remote system remained in that state afterward. Share recordings only with people who are allowed to see the terminal output and commands. Recording can contain hostnames, addresses, data, and secrets printed by a remote system.

​

Remote files over SFTP

For an SSH-capable host, select the host in Files and browse its remote filesystem over SFTP. Remote files open in Studio editors and save through the configured host session.

​

Create and organize documents

Create a file for a note, checklist, report, or source document that should exist independently of a single answer. Use clear, searchable names that include the site, service, date, or change identifier when relevant. Prefer a small number of meaningful folders over a deep hierarchy. Unified search and organization memory are designed to retrieve work by meaning and operational context.

​

Keep durable work trustworthy

• Include source timestamps and time zones in reports.
• Link or name the host, connector, tenant, and procedure that produced evidence.
• Mark assumptions and unverified conclusions.
• Store secrets in Key Chain, never in an artifact or organization memory.
• Verify generated code and app permissions before execution.
• Archive stale operational views and keep historical reports clearly dated.

​

Troubleshooting

​

Related