Perplexity launched Projects for long-running tasks in Perplexity Computer. Each project uses a shared workspace with a filesystem. Work stays durable beyond any single agent session. Multiple users and agents can edit in parallel without overriding each other. Users and agents can see the full history and roll back edits. The system uses a Git-based architecture with five cloud components. A CLI manages local checkouts and syncs changes in each sandbox. A control plane locates repositories and issues short-lived credentials. A Git service handles repository data and decides which submissions become commits. AWS S3-backed storage holds repository data durably. Downstream processing extracts text from saved documents for agent use. Agents work in isolated sandboxes with local repository copies. The CLI fetches and submits changes through the Git service.
What changed
Projects in Perplexity Computer did not keep work persistent, concurrent, or traceable across sessions, agents, and users.
What it unlocks
Running long tasks in Perplexity Computer with shared state that survives agent restarts and user sessions.
- <2% of submits rejected as stale
- median submit latency under 1.7 seconds
- p99 latency under 8 seconds
- warm checkout in 2.9 seconds
What you need to act on it
- a Perplexity Computer project
- a paid Perplexity plan
Sources