@papi-ai/server 0.7.15 → 0.7.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -6
- package/dist/index.js +2826 -925
- package/dist/prompts.js +26 -18
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -39,13 +39,9 @@ That's it. You're planning.
|
|
|
39
39
|
|
|
40
40
|
PAPI collects anonymous usage data (tool name, duration, project UUID — no code or task content). To opt out, add `PAPI_TELEMETRY=off` to your `.mcp.json` env block.
|
|
41
41
|
|
|
42
|
-
###
|
|
42
|
+
### Hosted backend
|
|
43
43
|
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
When the warning fires, PAPI emits an anonymous install-level ping (random UUID stored at `~/.papi/install-id.json`, chmod 600) per tool call so we can count installs that haven't connected yet. The ping contains: install UUID, tool name, server version, duration. **No project content, no file paths, no user identifiers.** Setting `PAPI_TELEMETRY=off` disables both the hosted-dashboard telemetry and the md-mode ping.
|
|
47
|
-
|
|
48
|
-
The warning is informational, not an error — md mode is a fully supported way to self-host PAPI without the hosted backend.
|
|
44
|
+
PAPI is configured with `PAPI_PROJECT_ID` and `PAPI_DATA_API_KEY` — both are generated by the onboarding wizard at [getpapi.ai](https://getpapi.ai/) and pasted into your `.mcp.json`. If those env vars aren't set, PAPI will fall back to local file storage (md mode) and emit a stderr warning that your cycles aren't visible on the dashboard. To get on the dashboard, sign up at [getpapi.ai](https://getpapi.ai/) and use the config it gives you.
|
|
49
45
|
|
|
50
46
|
## License
|
|
51
47
|
|