Compare commits
2 Commits
codex/issu
...
codex/issu
| Author | SHA1 | Date | |
|---|---|---|---|
| 440a46c8b5 | |||
| c86407d4f8 |
@@ -1,6 +1,6 @@
|
||||
# Agent Handoff
|
||||
|
||||
Last updated: 2026-07-04
|
||||
Last updated: 2026-07-05
|
||||
|
||||
## Latest Completed Work
|
||||
|
||||
@@ -17,6 +17,11 @@ Last updated: 2026-07-04
|
||||
- Live Dockge verification on 2026-07-04 used `LLM_TIMEOUT_MS=300000` and `LLM_MAX_TOKENS=4096` with the `heim-llm` LiteLLM alias. The completed sweep produced six parsed ideas, reported `ideasSource=llm`, persisted memory, and had no `lastSweepError`.
|
||||
- Production implementation commit: `14d9276c30e06cafcaee8177ba7377fdf5f26277`.
|
||||
- Issues #47, #51, and #53 are complete. Issue #21 tracks the failing security scan and #45 tracks the dependency workflow.
|
||||
- PR #57 / issue #56 added conversational Telegram AI chat for normal text plus `/ask` and `/reset`, bounded in-memory history, current intelligence grounding, typing activity, strict chat allowlisting, and plain-text replies.
|
||||
- Private Telegram chat messages are excluded from OSINT ingestion, and polling is serialized while a model response is running.
|
||||
- Gitea Actions runs 263-267 passed for the feature and production merge.
|
||||
- Live Dockge verification on 2026-07-05 reported `telegramAiChat.enabled=true`. A real `heim-llm` question using current dashboard context completed in 34 seconds and the answer was delivered successfully through the configured Telegram bot.
|
||||
- Current Telegram-chat implementation commit: `c86407d4f8bfb8a445bb7f4685ff545b479244a1`.
|
||||
|
||||
## Repository State
|
||||
|
||||
|
||||
Reference in New Issue
Block a user