Organize Your Zo Workspace

Your Zo Computer workspace is a real Linux filesystem. Every file you create, every project you build, every document your agents produce lives in /home/workspace. Over time, it accumulates. Without some structure, you end up scrolling through a flat list of files wondering where that script went.

The good news: your Zo can organize it for you. But "organize my files" is a vague instruction, and vague instructions produce vague results. This guide covers how to think about workspace structure so your Zo keeps things where you can find them.

Start with a folder structure that matches how you work

Most workspaces benefit from a handful of top-level directories based on what the files are for, not what type they are. A common layout:

• Code/ — Git repos, scripts, anything you run
• Documents/ — Notes, meeting summaries, drafts, anything you read
• Data/ — CSVs, JSON files, API responses, anything agents collect
• Projects/ — Active project folders with mixed content
• Archive/ — Finished work you want to keep but don't need daily

Ask your Zo to set this up:

Your Zo reads each file, infers what it is, and puts it where it belongs. A Python script goes in Code. A meeting-notes markdown file goes in Documents. A CSV of scraped prices goes in Data.

Use AGENTS.md as workspace memory

Your Zo reads a file called AGENTS.md at the root of your workspace at the start of every conversation. This is the single most effective way to keep your Zo aligned with how you organize things.

A good AGENTS.md tells your Zo where things live and how you like them:

Now every conversation starts with your Zo already knowing the layout. When it creates a file, it puts it in the right place without you specifying the path every time.

Update this file as your workspace evolves. When you start a new project, add a line about it. When a project wraps up, move it to the "completed" section. Your AGENTS.md is a living document, not a set-it-and-forget-it config.

Keep agent output organized automatically

If you run scheduled agents, their output accumulates fast. A daily news digest produces 365 files a year. Without a convention, they pile up in whatever directory the agent happened to write to.

Set a pattern early:

Adding this to your AGENTS.md means every agent follows the convention automatically, even new ones you create later.

For agents that produce structured data (JSON, CSV), keep those separate from prose output:

Find anything instantly

You don't need to memorize your file layout. Ask your Zo to search:

• Find all files I created this week
• Where's the script that processes Stripe webhooks?
• Show me everything related to the client onboarding project
• Find any Python files that import requests

Your Zo searches by filename and content. If you name files descriptively and keep notes in markdown, search works well. If everything is named untitled.txt and script.py, it doesn't. Naming matters.

Good file naming conventions:

• Date-prefix for time-sensitive files: 2026-03-09-standup-notes.md
• Descriptive names for scripts: scrape-product-prices.py instead of script.py
• Project prefix for cross-cutting files: onboarding-checklist.md, onboarding-email-templates.md

Connect your workspace to Google Drive

Your workspace and Google Drive are two sides of the same coin. Drive has documents your team shares. Your workspace has files your Zo works with. Connecting them lets your Zo pull Drive content into your workspace or reference Drive files without downloading them.

Common patterns:

• Download my Q1 planning doc from Drive and save it to Documents/planning/
• Search Drive for any spreadsheets with 'budget' in the name and summarize them
• Every Monday, check Drive for files shared with me in the last week and list them

Your Zo doesn't duplicate your entire Drive. It pulls specific files when you need them and works with them locally. This keeps your workspace lean while giving you access to everything in Drive.

Automate cleanup

Workspaces get messy over time. Temporary files accumulate, old agent output piles up, and one-off scripts linger. Set up periodic cleanup:

You can also set rules for how your Zo handles new files:

Project-based organization

For active projects with multiple related files, create dedicated project folders:

A project folder might look like:

Projects/client-onboarding/
  README.md          -- what this project is about
  docs/              -- specs, notes, drafts
  scripts/           -- automation code
  data/              -- input files, generated output

The README serves as project-level AGENTS.md. When you tell your Zo to "work on the onboarding project," it reads the README and knows the context.

Templates for repeated work

If you create the same type of file regularly (weekly reports, meeting notes, project briefs), set up templates:

Templates keep your output consistent and save your Zo from reinventing the format each time. Pair this with a persona that knows your preferred writing style, and your documents are both organized and well-written.

Getting started

Start simple. Get the basic folder structure in place and create an AGENTS.md:

From there, build habits. Name files well. Keep agent output in one place. Archive old work. Your workspace should feel like a well-organized desk, not a junk drawer.