dsh-web-search-perplexity

Configuration

Mounting is automatic; selecting it as the active provider and tuning it happen in the profile's cordis.patch.yml:

- id: web
  config:
    searchProvider: perplexity-account
- id:    # shown in Settings → Plugins → Plugin list
  config:
    sessionToken: !!js process.env.PERPLEXITY_SESSION_TOKEN  # or leave unset and sign in via the authorization UI
    model: experimental          # consumer model_preference; default 'experimental'
    searchRecency: week          # optional: hour|day|week|month|year
    timeoutMs: 60000             # optional

Field	Default	Meaning
cookies	$PERPLEXITY_COOKIES	Raw Cookie header from a logged-in perplexity.ai session (highest precedence)
sessionToken	$PERPLEXITY_SESSION_TOKEN	Value of __Secure-next-auth.session-token; falls back to the credential record
apiKey	$PERPLEXITY_API_KEY	Billed Sonar API key; falls back to the api-key credential record
openRouterKey	$OPENROUTER_API_KEY	OpenRouter key — routes perplexity/
model	experimental	Consumer model_preference (Sonar on paid plans)
apiModel	sonar-pro	API-mode model
apiMaxTokens	8192	API-mode max_tokens
apiTemperature	0.2	API-mode sampling temperature
numSearchResults	20	API-mode num_search_results
useResponsesApi	$PERPLEXITY_RESPONSES=1	API-mode transport: Responses API SSE instead of chat/completions
searchRecency	(unset)	search_recency_filter: hour, day, week, month, year
timeoutMs	60000	Hard per-request timeout

To sign in interactively, run the harness's login/authorization UI and pick Perplexity (account session) — browser SSO is the default method — or Perplexity (API key) to store a Sonar API key. In the web interface, the plugin appears as Enabled under Settings → Plugins → Plugin list → Global plugins; no card is rendered under Plugin configuration (which requires a client-side browser bundle), so tuning parameters are configured exclusively via the profile patch (cordis.patch.yml) or environment variables.