Big ideas.
A team to build them.

The idea behind the workspace

Working with several agents can scatter context across conversations, tools, and files. Zipper brings those pieces into a desktop workspace: teammates have roles, projects carry the brief, and agent computers hold the working output.

The goal is to make it easier to move from a request to a result you can inspect. You should be able to see who is working, follow a handoff, find the files, and understand which decision is needed next.

What guides the product

1. Make work visible.

   Progress, questions, and blockers belong where the user can find them. A final summary is more useful when the underlying conversation and output are available.

2. Keep context with the project.

   A shared brief, notes, and files make the next task easier to pick up. Give teammates clear ownership when they work in parallel.

3. Leave room for judgment.

   Agents can prepare, build, and review, but their reports can be wrong. Make it easy for a person to inspect the evidence and decide what happens next.

Keep the work portable

Zipper’s original code and artwork are MIT licensed. The workspace lives on the host you choose, and you choose supported model connections and tools. Those providers and dependencies keep their own charges, policies, and license terms.

Project files are valuable outside the conversation that created them. Keeping the output available helps you continue in your own tools and make the next change.

Where the project is today

Zipper is in preview. The website is public, and the download page lists desktop preview availability. Application source publication is being prepared separately. Current guides distinguish tested flows from platform work still ahead.