TL;DR
Please add user-defined keyword rules so that when a new chat contains specified words, it is automatically assigned to a chosen Space.
Problem
Spaces are great for organizing topic- or project-based research, but currently I have to remember to add each new chat to the right Space manually after it’s created. This makes it easy for related threads to end up scattered across my general history instead of staying grouped in the appropriate Space.
Requested feature
Add support for user-defined routing rules so that new chats can be automatically assigned to a Space based on keywords in the initial query.
Example
I have an “Alaska” Space where I’m planning a trip. I’d like to define rules so that any new chat whose initial query contains “Alaska,” “Kodiak,” or “Anchorage” is automatically assigned to that Space, instead of starting in the default workspace.
Proposed behavior (MVP)
Let users create one or more rules of the form: “If the initial query contains keyword(s) X, assign the chat to Space Y.”
Support multiple keywords per rule.
Rules apply only to newly created chats going forward.
Users can still manually remove or reassign a chat to a different Space at any time.
Nice-to-have extensions
Match mode: “match any keyword” vs. “match all keywords.”
Ability to apply a rule retroactively to existing history in bulk.
Option to match against both the initial query and the thread title.
A simple “Routing rules” panel inside each Space or in global settings to review, enable/disable, and edit rules.
Why this matters
Spaces are meant to help organize and work with collections of related material, but without light automation they still require manual filing after the fact. Keyword-based routing would make Spaces much more useful for ongoing projects and recurring research topics.
One-line summary:
Please add keyword-based automatic assignment of new chats to user-selected Spaces.
Pre-flight checklist
- This is a Perplexity API feature request, not a Perplexity app, Comet, or web UI request.
- I have checked whether this already exists in the docs or another forum topic.
- I have described the developer workflow or API use case this would improve.
Feature type
- New endpoint or API capability
- New model, preset, or model behavior
- New parameter or request option
- New response field or metadata
- SDK improvement
- Dashboard, API key, or auth improvement
- Billing, credits, rate limit, or usage reporting improvement
- Docs or examples improvement
- Other API improvement
Affected API area
- Agent API
- Search API
- Sonar API
- Embeddings API
- SDKs
- Dashboard, API keys, or auth
- Billing or credits
- Not sure
Summary
Problem
Proposed API behavior
Example usage