You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: address 4 issues found in post-v0.2.2 commits (#49)
- Restore missing ALTIMATE_CLI_LIBC build define dropped when OPENCODE_*
constants were removed, fixing file watcher on musl Linux
- Correct security FAQ claim that conversation history is not persisted;
sessions are stored in SQLite and prompt history on disk
- Guard session_end telemetry in finally block with dedup flag to prevent
duplicate events when emergency handler already fired
- Remove unused Filesystem import in worker test
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/docs/security-faq.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,12 @@ The engine is not exposed on any network port — it only communicates through s
150
150
151
151
## Does Altimate Code store conversation history?
152
152
153
-
Conversation context lives in memory during your session. Altimate Code does not persist conversation history to disk or send it to any service. When you end a session, the context is gone.
153
+
Yes. Altimate Code persists session data locally on your machine:
154
+
155
+
-**Session messages** are stored in a local SQLite database so you can resume, review, and revert conversations.
156
+
-**Prompt history** (your recent inputs) is saved to `~/.state/prompt-history.jsonl` for command-line recall.
157
+
158
+
This data **never** leaves your machine — it is not sent to any service or included in telemetry. You can delete it at any time by removing the local database and history files.
154
159
155
160
!!! note
156
161
Your LLM provider may have its own data retention policies. Check your provider's terms to understand how they handle API requests.
0 commit comments