Details
- Perplexity describes Projects as a shared Git-based workspace where agents and people can build on work across sessions.
- Each agent operates in an isolated, ephemeral sandbox with its own checkout of the project repository.
- Git provides atomic multi-file commits, authorship, persistence, and searchable history, while a repository contract replaces conventional pull-request review.
- A short-lived CLI lock serializes submissions, and the Git service accepts a change only when it is based on the latest accepted commit.
- If another agent submits first, the later agent rebases or replays its changes on the new repository head before resubmitting.
- Repositories use S3-backed storage rather than long-lived sandboxes, reducing infrastructure requirements and limiting crashes to unsubmitted work.
- Agents search real checkouts with grep and standard file tools; Perplexity reports 0.627 accuracy on an internal 150-question financial-document benchmark, compared with about 0.37 for semantic search.
- The architecture supports persistent shared files while allowing independent agents to work concurrently without overwriting one another.
Impact
The design shifts agent collaboration toward version-control infrastructure rather than transient chat context. Persistent repositories, isolated execution, and commit-level concurrency controls could make long-running multi-agent workflows easier to audit and recover, while the reported benchmark suggests conventional file tools may outperform broad semantic retrieval for structured document tasks. The approach also creates an operational foundation for Projects to scale agent workloads without maintaining continuously provisioned sandboxes.