Ok cool, sounds good, yes, please

[ojhurst]

So I noticed that sometimes when I'm just basically acknowledging a proposed plan from Claude Code, for example, I will respond in the affirmative, right? Okay, cool, sounds good, go ahead, yes, please. Little two-word answers, and I'm noticing that I'm getting like random memories from Signet inserted into the context at that point in time, and I'm just thinking that it shouldn't be that way. I'm wondering if that's a bug, if that's by design, or just what's going on.

[NicholaiVogel]

Hello, @ojhurst yes, these injections are triggered by the userpromptsubmit hook, as it operates
on every turn, injecting context like the date & time as well as some general context and memories.

it looks like this:

# Current Date & Time
Tuesday, May 26, 2026 at 2:17 PM (America/Denver)

## Memory Check

Use the Signet context below as starting context before acting. Codex native memory is already available separately, so run 1-3 targeted Signet recalls with signet_recall only when the task needs cross-harness history, source-backed artifacts, sessions, ontology, or accepted decisions. Ask natural questions with entity + event + timeframe when possible. Avoid bag-of-keywords recall queries. Treat graph expansion as supporting context, not proof.

## Relevant Memory

- [thread 2fd91d96-a426-4299-831a-bba9d5d2a491] ...name}"` to detect when a bot has been mentioned in thread history, but this pattern only matches bot mentions that appear at the start of a comment body. ### Root Cause The `build_thread_history` function formats thread entries as `- [timestamp] login: body`, where the `": "` sep... (Mar 30, 2026, project:/mnt/work/dev/signet/signetai2#source:3613108a-f184-470a-97ff-4a898f5e8fca#harness:codex)

If you learn something explicitly durable for Codex memory, save it with signet_save_note.

When there's no relevant memory injections found, it will say that plainly and return no memories, but it's something that's always on. I wonder often if this is something that is too intrusive to run on every turn and maybe if it would be better to have a configurable inject after every n turns sort of behavior, but I'm curious what you think?

[NicholaiVogel]

and I suppose if we listen for exact keywords like Okay, cool, sounds good, go ahead, yes, please that would work as well, but I would imagine a mix of both would be best.

[ojhurst]

I think in my case it was for whatever reason, whether it was a bug or something not quite tuned properly. I said, okay, cool. It surfaced essentially random memories that it should not have. Really, on okay, cool, there's really nothing to surface. And so it just, I don't know, to me it just kind of raised that use case essentially raised at least a gap, some sort of gap that I think could be looked at or filled.

[NicholaiVogel]

Less of a gap and more of a refinement, probably. I'll look into it!