refactor(search): always send searches as incognito (#14)
Hardcode is_incognito: true in the Perplexity request and remove the toggle surface: the incognito tool parameter, PI_PERPLEXITY_INCOGNITO env var, config file field, /perplexity-config prompt, and TUI status indicators. Config and resolveDefaultModel are now model-only. Supersedes the incognito portion of PR #4. Co-authored-by: Ivan Pereira <183991+ivanrvpereira@users.noreply.github.com>
This commit is contained in:
co-authored by
Ivan Pereira
parent
a9f252715e
commit
97aab3e9b9
@@ -45,7 +45,7 @@ node --no-deprecation --import ./node_modules/@earendil-works/pi-coding-agent/no
|
||||
|
||||
- Endpoint: `POST https://www.perplexity.ai/rest/sse/perplexity_ask`.
|
||||
- Required Perplexity constants live in `src/constants.ts`.
|
||||
- Searches default to `is_incognito: true` to avoid polluting user history.
|
||||
- Searches always send `is_incognito: true` to avoid polluting user history; there is no toggle.
|
||||
- The response is `data:` JSON lines with `[DONE]`, not a fully standard SSE stream.
|
||||
- Events are incremental snapshots: shallow-merge top level, merge blocks by `intended_usage`, splice markdown via `chunk_starting_offset`, accumulate sources.
|
||||
- Completion is `event.final === true` or `event.status === "COMPLETED"`.
|
||||
|
||||
Reference in New Issue
Block a user