feat: prepend time-gap notice to user message when >5 min elapsed #10

2026-02-19T00:32:50+01:00

wylab commented

2026-02-19 00:32:50 +01:00

Summary

Adds time-gap awareness to _process_message in nanobot/agent/loop.py
When >5 minutes have passed since the last user message in a session, prepends [SYSTEM ANNOUNCEMENT: X minutes/hours/days have elapsed since last user message] to the current message content
Keeps the LLM aware of real time elapsed between conversation turns

Implementation Details

Walks session.messages in reverse to find the last user message timestamp
Uses datetime.fromisoformat() to parse the stored ISO timestamps
Threshold: 300s (5 min) → formats as minutes, hours, or days
Malformed timestamps silently skipped (try/except)
Note: session.add_message("user", ...) runs after build_messages, so the reversed walk finds the previous user message — no off-by-one issue
Only affects _process_message; _process_system_message (subagent announces) is unchanged

Test plan

Send two messages with >5 min gap — second message should log with [SYSTEM ANNOUNCEMENT: X minutes have elapsed...] prefix
Send two messages with <5 min gap — no prefix injected
Verify new session (no prior messages) — no prefix injected

🤖 Generated with Claude Code

## Summary - Adds time-gap awareness to `_process_message` in `nanobot/agent/loop.py` - When >5 minutes have passed since the last user message in a session, prepends `[SYSTEM ANNOUNCEMENT: X minutes/hours/days have elapsed since last user message]` to the current message content - Keeps the LLM aware of real time elapsed between conversation turns ## Implementation Details - Walks `session.messages` in reverse to find the last user message timestamp - Uses `datetime.fromisoformat()` to parse the stored ISO timestamps - Threshold: 300s (5 min) → formats as minutes, hours, or days - Malformed timestamps silently skipped (try/except) - Note: `session.add_message("user", ...)` runs **after** `build_messages`, so the reversed walk finds the *previous* user message — no off-by-one issue - Only affects `_process_message`; `_process_system_message` (subagent announces) is unchanged ## Test plan - [ ] Send two messages with >5 min gap — second message should log with `[SYSTEM ANNOUNCEMENT: X minutes have elapsed...]` prefix - [ ] Send two messages with <5 min gap — no prefix injected - [ ] Verify new session (no prior messages) — no prefix injected 🤖 Generated with [Claude Code](https://claude.ai/claude-code)

wylab added 1 commit 2026-02-19 00:32:51 +01:00

feat: prepend time-gap notice to user message when >5 min elapsed

Build Nanobot OAuth / cleanup (pull_request) Has been skipped

Details

Build Nanobot OAuth / build (pull_request) Successful in 5m34s

Details

dde242d170

Adds elapsed-time awareness to _process_message. When >5 minutes have
passed since the last user message in a session, prepends a SYSTEM
ANNOUNCEMENT header so the LLM knows time has passed.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

code-server added 1 commit 2026-02-19 00:55:03 +01:00

debug: add time-gap instrumentation logs

Build Nanobot OAuth / cleanup (pull_request) Has been skipped

Details

Build Nanobot OAuth / build (pull_request) Successful in 5m32s

Details

da7f58d3cc

code-server added 1 commit 2026-02-19 01:04:24 +01:00

chore: remove debug logs from time-gap injection

Build Nanobot OAuth / cleanup (pull_request) Has been skipped

Details

Build Nanobot OAuth / build (pull_request) Successful in 6m29s