day-recap
Collects a day's work from local git repositories, Cursor transcripts, OpenCode sessions, and a Telegram allowlist. Only a confirmed block is appended to the Obsidian daily note.
The raw dump stays outside the vault. An empty day does not change the note.
## 🤖 Итоги дня
### Сделано
- **billing** — сузил окно повторной оплаты до одного счёта
### Решения и обоснования
Оставили повтор по idempotency-key. Повтор всей корзины отбросили: он списывал деньги второй раз.
Install and configure
From a checkout of this repository:
uv tool install --editable .
mkdir -p ~/.config/day-recap
cp config.example.toml ~/.config/day-recap/config.toml
Run day-recap init in your own terminal, not in the agent chat. Do not
type api_id or api_hash into the chat. init asks qr or code. qr
prints a code to scan: Settings → Devices → Link desktop device. code waits
for the login code in the Telegram service chat. --login qr or --login code
skips the question. --relogin signs in again.
day-recap chats prints a table and ready [[telegram.chats]] blocks.
Paste the blocks you want into the [telegram] section. Only those chats are
read into the raw dump.
| Section | What it sets |
|---|---|
[notes] |
Where to write the daily note. |
[state] |
Where raw dumps are stored. |
[git] |
Which directories to walk and whose commits to take. |
[transcripts] |
Cursor JSONL roots and how messages are trimmed. |
[opencode] |
OpenCode database and the same trim. |
[telegram] |
Whether the source is on, and the allowlist. |
[summary] |
Size threshold. |
Keys and defaults are in config.example.toml.
- The size threshold is 100000 bytes.
- Raw dumps are kept for 14 days.
~/.config/day-recap/.envis mode 600.
In the agent
Copy SKILL.md to ~/.agents/skills/day-recap/SKILL.md.
/day-recap
/day-recap yesterday
/day-recap 2026-10-05
The date is today, yesterday, or YYYY-MM-DD. With no date, the window
runs from local midnight to the moment you start.
The skill shows a draft and asks what you decided and what you rejected. The note changes only after a separate yes. An empty day does not change the note. With no Telegram session the other sources are still collected, and the block contains the line «Telegram недоступен, чаты не учтены».
Other commands
collect stores a raw dump. show prints the day status, or one source when
you name it. The source is optional: git, transcripts, opencode, or
telegram. Both take --date (today, yesterday, or YYYY-MM-DD) and
--config PATH.
write reads the block from stdin. It needs --date YYYY-MM-DD and
--body -, and takes --config PATH. Without --apply the note stays
unchanged.
day-recap collect --date yesterday
day-recap show git --date 2026-10-05
day-recap write --date 2026-10-05 --body - --apply
Development
just lint # ruff
just fmt # ruff format
just types # mypy
just test # pytest
Metadata
Release files for day-recap 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| day_recap-0.2.1.tar.gz | 43.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| day_recap-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 98.1 kB
Release files / day_recap-0.2.1.tar.gz
| Download URL | day_recap-0.2.1.tar.gz |
|---|---|
| Size | 43.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff07ae747052137b55525994bf014b9b1394d9c9189ecaac5baf233dd430cb12
|
|
BLAKE2b-256 checksum How to use checksums |
961030b550032b4202fb7d96444748684ee200ea1494a36c4628c113adc6a458
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / day_recap-0.2.1-py3-none-any.whl
| Download URL | day_recap-0.2.1-py3-none-any.whl |
|---|---|
| Size | 54.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d268156e23594e617da4996dfb065b9b112ad06540091f3acd47594c7c2821f
|
|
BLAKE2b-256 checksum How to use checksums |
1b7cbce13c1ed617fd5c48164a34f655722b6aae564807e595e655dc098d404d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency log