ambient context: give every project's model a clock #135
Reference in New Issue
Block a user
Delete Branch "feat/ambient-context"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Models consuming projects don't know today's date. Always-on, for every project:
[context] now: Thu 2026-10-02 10:30 +01:00 Europe/London (09:30 UTC) — project: <name>(frozen at session start by design);get_current_timevirtual tool (ungated catalogs, same pattern asread_prompts);tools/callresponse gets a trailing[context] now: …content item at the endpoint send site — covers upstream results, virtual tools, gate intercepts and failure results, and keeps a days-old LibreChat session on today's date (~15 tokens, minute precision, appended as a separate item so JSON-parsing clients are untouched);MCPLOCAL_AMBIENT_TZ(IANA name, read by both services) adds the local rendering; unset/invalid → UTC only.Tests: new
ambient-time,plugin-ambient-context,project-mcp-endpoint-ambientsuites + extended gate/endpoint/chat-service assertions. Full./tests.sh --shortgreen (the one mcpd failure was a missing localprisma generate, pre-existing).🤖 Generated with Claude Code