[FEATURE]:Auto-timestamp on user messages for AI time context #47251

Activity

1. github-actions

   assigned

   nexxeln

   on Sep 4, 2026
2. github-actions commented on Sep 4, 2026

   

   github-actionsBot

   on Sep 4, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of an existing issue. Please check:

   • [FEATURE]: Inject per-message timestamps as AI-visible context #15876: [FEATURE]: Inject per-message timestamps as AI-visible context — same request to automatically include current date/time in messages so the AI has temporal context.
3. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the suggestion! You're asking for each user message to carry a timestamp (date and time of day) so the model always knows the current time in long or multi-session work.

   For context: OpenCode v2 already tells the model today's date and sends an update when the date changes during a session. It doesn't include the time of day or a timestamp on each message. Maintainers will consider this; I can't promise anything.

   Related issues:

   • [FEATURE]: Ensure fresh time context for recurring/loop-triggered prompts in long-lived sessions (complement to #47816) #48639: follow-up asking for a fresh time context on every turn, including prompts sent by automation (cron, schedulers)
   • [FEATURE]: Inject per-message timestamps as AI-visible context #15876: an earlier request for per-message timestamps that was closed automatically for inactivity

   In the meantime, a small v2 plugin can do this today. It adds the local time to the start of every prompt you send. It type-checks against the plugin API, but I haven't tested it in a running OpenCode. Save it as ~/.config/opencode/plugins/timestamp.ts to use it everywhere, or as .opencode/plugins/timestamp.ts for a single project:

   import { Plugin } from "@opencode/plugin"
   
   const pad = (n: number) => String(n).padStart(2, "0")
   
   const stamp = (d: Date) => {
     const offset = -d.getTimezoneOffset()
     const sign = offset >= 0 ? "+" : "-"
     const tz = `${sign}${pad(Math.floor(Math.abs(offset) / 60))}:${pad(Math.abs(offset) % 60)}`
     return `${d.getFullYear()}-${pad(d.getMonth() + 1)}-${pad(d.getDate())} ${pad(d.getHours())}:${pad(d.getMinutes())} ${tz}`
   }
   
   export default Plugin.define({
     id: "user-message-timestamp",
     setup: async (ctx) => {
       await ctx.session.hook("prompt", (event) => {
         event.prompt.text = `[${stamp(new Date())}] ${event.prompt.text}`
       })
     },
   })

   The timestamp becomes part of the saved message, so you'll also see it in the conversation (e.g. [2026-09-04 16:05 +02:00] your message). Restart the background service with opencode service restart so it picks up the plugin.