The left-hand panel in Context is your team’s workspace history. It’s divided into two distinct sections:
  1. Artifacts — polished, interactive outputs created by Context during your sessions
  2. Computer Files — behind-the-scenes system files generated during code execution and data processing
Use Artifacts to work with finished or work-in-progress deliverables; use Computer Files to inspect how results were produced.

​
1) Artifacts (Top Section)

​
What are Artifacts?

Artifacts are rich, interactive outputs produced by Context—think documents, presentations, code projects with live previews, spreadsheets, and data visualizations,. They’re designed for review, iteration, and export.

​
Core Actions

  • Grid view: Browse your artifacts as visual cards in a 2–4 column grid.
  • Open & interact: Click any card to launch a full-screen, interactive view.
  • Live editing (where applicable): Modify code or content and see changes instantly.
  • Version history: Review prior versions, compare diffs, and restore if needed.
  • Export & share: Download files or share with teammates according to workspace permissions.

​
2) Computer Files (Bottom Section)

​
What are Computer Files?

This section lists internal system files produced when Context executes code or processes data during your session—useful for transparency, troubleshooting, and reproducibility. Typical sources include:
  • Code execution (e.g., Python scripts)
  • Data processing (CSV/JSON outputs, aggregates)
  • Generated assets (images, charts)
  • Simulations & tests (model artifacts, logs, results)

​
Organization

Files are stored in a structured, project-scoped hierarchy: 
Home/Tasks/[Your Project]/Computer Files/
├── code_execution_outputs/
├── data_analysis_results/
├── generated_assets/
└── temporary_files/

​
Behavior & Permissions

  • Read-only: Managed automatically by Context; not intended for manual edits.
  • Internal use: Provided for auditability and reference.
  • Safe to browse: Open and view files without affecting runtime state.
  • No manual upload: This area is system-controlled.
  • Project-specific isolation: Each conversation has its own file space.

​
File Types You’ll See

  • Code: .py and related execution artifacts
  • Data: .csv, .json, intermediate tables, summaries
  • Images: .png, .jpg (charts, diagrams, thumbnails)
  • Text: .txt, .md for logs or analyses
  • Configs: Parameters and settings captured during runs
Panel controls
  • Resize: Drag the divider to adjust width.
  • Independent scrolling: Artifacts and Computer Files scroll separately.
  • Search & filter: Use the breadcrumb and quick filters to narrow results.
Quick actions
  • Open an Artifact: Launches the interactive editor/viewer.
  • Open a File: Uses the appropriate viewer (code editor, data/table view, image preview, PDF viewer, etc.).
  • Breadcrumbs: Jump quickly between folders and project scope.
  • Back to Project: Return to your project root at any time.

​
Best Practices (Enterprise)

  • Review Artifacts regularly: Capture and reuse high-value outputs as canonical references.
  • Leverage version history: Use diffs to explain changes and support approvals.
  • Inspect Computer Files for transparency: Understand intermediate steps, parameters, and datasets used to produce results.
  • Share with intent: Artifacts respect workspace permissions; share only what stakeholders need.
  • Stay organized: Artifacts are auto-sorted by newest first; pin or name consistently for quick retrieval.

​
FAQ

Can I edit files in Computer Files?
No. They’re read-only and system-managed to preserve provenance. How do I export an Artifact?
Open the Artifact and use Export (download/share). Options vary by artifact type (e.g., PPTX, PDF, code bundle). What if I need to reproduce a result?
Use version history for Artifacts and review Computer Files (configs, intermediate outputs) to trace the exact steps and parameters. Who can see my Artifacts and files?
Visibility follows your workspace and project permissions set within Context.
The Artifacts & File Panel gives your team both a polished output layer and a technical audit trail—helping you ship professional deliverables while maintaining clarity on how they were built.