amadan
docs/site/cli.md: explain carlos db --at (#262)
Paragraph approved in copy review 2026-10-08, unedited. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Human
Prompt
Yes, go ahead.
From this commit's own message. The prompt ledger has no entries for it — which is what a squashed, rebased or amended commit looks like, and what every commit looks like in a repo without a ledger.
Summary
Documents --at in the public CLI reference.
1 file changed,
+8
−0
docs/site/cli.md+8 −0
CI cancelled — superseded by a newer push — run details
diff --git a/docs/site/cli.md b/docs/site/cli.md| index 44dc7d488..489572e6f 100644 |
| --- a/docs/site/cli.md |
| +++ b/docs/site/cli.md |
| @@ -459,6 +459,14 @@ Both say how recent the copy is: the last transaction it holds, and when |
| that transaction was written. A sleeping instance's copy is as recent as its |
| last sync before it went to sleep. A busy instance can be ahead of its copy. |
| +To read the database as it was at an earlier time, add `--at` with a time |
| +in RFC 3339 form, such as `--at 2026-10-07T14:00:00Z`. The copy holds every |
| +change replicated before that time. It can be a little older than the time |
| +you give, never newer, and the command says which transaction it stopped |
| +at. How far back you can go depends on how much history the platform keeps |
| +for the instance. Ask for a time earlier than that and the command names |
| +the oldest time you can use instead. |
| + |
| The copy is read-only. A query that tries to change it fails with SQLite's |
| own error, `attempt to write a readonly database`. That is on purpose. |
| Changing a copy would change nothing on the instance, and a command that |