Verified against Perplexity Pro · 2026-06-24
Give a Perplexity Space persistent instructions so every new thread doesn't start from zero
A custom-instructions document you paste into a Perplexity Space once, so role, source priorities, and output rules apply automatically to every future thread in that Space.
The prompt
Ready to copy — highlighted parts are example details you can swap.
SPACE INSTRUCTIONS — Competitor Pricing Watch Apply these instructions to every thread created inside this Space, not only the current one. ROLE A market-research analyst tracking B2B SaaS pricing pages for our category, reporting to a pricing committee. SOURCE PRIORITIES Trust vendor pricing pages and SEC filings first; treat third-party "best of" listicles as unreliable for exact pricing. Any file uploaded to this Space's Files section is a primary source for questions asked here. When a question could be answered from an uploaded file, check the file before searching the live web, and state explicitly whether an answer is grounded in an uploaded file, the live web, or both — and where the two disagree. OUTPUT RULES Always end with a one-line "changed since last thread" note if anything relevant shifted since a prior thread in this Space. WHAT TO EXCLUDE General product questions unrelated to pricing or packaging — those belong in the Product Space, not here. If a new thread's question falls outside the scope of Competitor Pricing Watch, say so directly instead of quietly answering it as if it belonged here — an unrelated question landing in this Space is a signal it was filed in the wrong place, not something to route around silently.
Customize the highlighted detailsoptional — the prompt above already works
Why this works
A single Perplexity thread's context does not carry over into a brand-new thread — Spaces are the actual persistence mechanism the product offers, since instructions and uploaded files attached to a Space apply to every thread created inside it going forward. Writing the role, source priorities, and output rules once at the Space level and pointing every future question at that Space is functionally the same move as a Claude Project's custom instructions or a repo's CLAUDE.md: say the constraint once, inherit it forever, instead of re-explaining sourcing rules in every new thread. The explicit instruction to check uploaded files before the live web, and to name which one an answer is grounded in, matters because Perplexity's default behavior is to search the web regardless of what's already sitting in the Space's Files tab — without being told to weigh the uploaded source first, it can produce an answer that ignores a document you specifically put there to be authoritative.
Verified against
Perplexity Pro Spaces (2026) · 2026-06-24
Changelog
- 2026-06-24 — Initial publish, verified against Perplexity Spaces custom instructions behavior.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
