Stop social prompts from tripping source grounding
This commit is contained in:
parent
95440a3af7
commit
9978fd3ef5
3 changed files with 7 additions and 4 deletions
|
|
@ -249,7 +249,7 @@ export function inferSourceGroundingHint(
|
|||
|
||||
for (const repo of repoSummaries) {
|
||||
for (const alias of buildRepoAliases(repo.repoName)) {
|
||||
if (alias.length < 4) {
|
||||
if (alias.length < 6) {
|
||||
continue;
|
||||
}
|
||||
|
||||
|
|
|
|||
|
|
@ -271,14 +271,16 @@ export async function startBot(): Promise<void> {
|
|||
return;
|
||||
}
|
||||
|
||||
const isDirectMessage = !message.inGuild();
|
||||
|
||||
await ingestIfIndexed(message, config.channelIndexing, ragPipeline);
|
||||
await rememberAmbientVoidReference(message, client.user?.id, interactionMemory);
|
||||
|
||||
if (!client.user || !message.mentions.has(client.user)) {
|
||||
if (!client.user || (!isDirectMessage && !message.mentions.has(client.user))) {
|
||||
return;
|
||||
}
|
||||
|
||||
const prompt = stripBotMention(message.content).trim();
|
||||
const prompt = isDirectMessage ? message.content.trim() : stripBotMention(message.content).trim();
|
||||
|
||||
if (!prompt) {
|
||||
await replyToMessage(
|
||||
|
|
@ -313,7 +315,7 @@ export async function startBot(): Promise<void> {
|
|||
providerRegistry,
|
||||
stylePack: activeStylePack,
|
||||
systemMessages: activeSystemMessages,
|
||||
silentOwnerQueueAck: true,
|
||||
silentOwnerQueueAck: !isDirectMessage,
|
||||
});
|
||||
} catch (error) {
|
||||
console.error(error);
|
||||
|
|
|
|||
|
|
@ -18,3 +18,4 @@
|
|||
{"ts":"2026-05-02T11:48:55Z","type":"implementation","status":"ok","note":"Source repo indexing now auto-reconciles during startup and watchdog runs, and the source archive is sharded by repo behind a manifest because the old monolithic source-documents.json hit real size limits and broke incremental writes."}
|
||||
{"ts":"2026-05-02T14:05:54Z","type":"implementation","status":"ok","note":"Scheduled-task helpers must anchor repo-relative scripts, dotenv loading, and path resolution to the VoidBot root; relying on cwd keeps sending System32 in to eat them."}
|
||||
{"ts":"2026-05-02T17:34:02Z","type":"implementation","status":"ok","note":"Layered private system message catalogs over the tracked base, deferred slow slash replies before provider execution, and chunked Discord output so missing keys and overlong local_llm replies stop failing live interactions."}
|
||||
{"ts":"2026-05-02T17:39:46Z","type":"implementation","status":"ok","note":"Source-grounding alias matching now ignores overly short repo components so social prompts mentioning Void stop tripping fake repo-evidence requirements, and direct messages intentionally count as prompts without requiring a mention."}
|
||||
|
|
|
|||
Loading…
Reference in a new issue