mirror of
https://github.com/qwibitai/nanoclaw.git
synced 2026-06-04 10:14:47 +08:00
gavrielc
16b9499532
Replaces the opaque trigger_rules JSON + response_scope enum on
messaging_group_agents with four explicit orthogonal columns:
engage_mode 'pattern' | 'mention' | 'mention-sticky'
engage_pattern regex source; required when mode='pattern';
'.' is the "always" sentinel
sender_scope 'all' | 'known'
ignored_message_policy 'drop' | 'accumulate'
Inbound routing becomes a fan-out — every wired agent is evaluated
independently. A match gets its own session + container wake. A miss
with accumulate keeps the message as context-only (trigger=0) in that
agent's session, so when the agent does eventually engage it sees the
prior chatter.
## Schema
- Migration 010 (`engage-modes`): adds the 4 new columns, backfills
from trigger_rules.pattern + requiresTrigger + response_scope, drops
the legacy columns.
- messages_in gains `trigger INTEGER NOT NULL DEFAULT 1` (session DB
schema + `migrateMessagesInTable` forward-compat).
- countDueMessages gates waking on `trigger = 1`.
## Routing
- `pickAgent` (returns one) → loop over all wired agents. Per agent:
evaluate engage_mode; run access gate + sender-scope gate; on full
match → resolveSession + writeSessionMessage(trigger=1) + wake. On
miss with accumulate → writeSessionMessage(trigger=0), no wake. On
miss with drop → skip.
- New `findSessionForAgent(agentGroupId, mgId, threadId)` scopes
session lookup by agent so fan-out doesn't cross sessions.
- `messageIdForAgent` namespaces inbound message ids by agent_group_id
so PRIMARY KEY doesn't collide across per-agent session DBs.
## Adapter layer
- `ConversationConfig` replaces `triggerPattern` + `requiresTrigger`
with `engageMode` + `engagePattern`.
- Chat SDK bridge stores `Map<platformId, ConversationConfig[]>` (multi-
agent per conversation) and applies union gating pre-onInbound:
* onSubscribedMessage: engage if any wiring keeps firing in
subscribed state (mention-sticky or pattern)
* onNewMention: engage on mention; only subscribes the thread if
at least one wiring is `mention-sticky`
* onDirectMessage: engage per mode; sticky follows same rule
- Bridge no longer unconditionally calls `thread.subscribe()`.
## Sender scope
- Permissions module registers a second hook `setSenderScopeGate` that
runs per-wiring after the existing access gate. `sender_scope='known'`
requires canAccessAgentGroup(); `'all'` is a no-op. Not installed →
no-op everywhere (default allow).
## Container side
- Host passes `NANOCLAW_MAX_MESSAGES_PER_PROMPT` (reuses existing
MAX_MESSAGES_PER_PROMPT config; was dead code from v1).
- `getPendingMessages` queries `ORDER BY seq DESC LIMIT N`, reverses to
chronological order for the prompt — accumulated context rides along
with trigger rows up to the cap.
- `MessageInRow` gains `trigger: number` so the container can tell them
apart in downstream code (container still processes both; only the
host uses `trigger=0` for don't-wake).
## Defaults (per ACTION-ITEMS item 1 decision)
- DM (is_group=0): `engage_mode='pattern'`, `engage_pattern='.'` (always)
- Threaded group: `engage_mode='mention-sticky'` (seed-discord)
- Non-threaded group / CLI: pattern '.' in bootstrap scripts
## Tests
- src/host-core.test.ts: 3 new cases — fan-out (2 agents, 2 sessions,
2 wakes), accumulate (trigger=0 + no wake), drop (no session created).
- Existing 10 host-core tests still pass.
- Migration 010 runs on an empty DB in 0-row path — verified.
Closes: ACTION-ITEMS items 1, 4.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
81 lines
2.3 KiB
TypeScript
81 lines
2.3 KiB
TypeScript
/**
|
|
* Seed the v2 central DB with a Discord agent group + messaging group.
|
|
*
|
|
* Usage: pnpm exec tsx scripts/seed-discord.ts
|
|
*/
|
|
import path from 'path';
|
|
|
|
import { DATA_DIR } from '../src/config.js';
|
|
import { initDb } from '../src/db/connection.js';
|
|
import { runMigrations } from '../src/db/migrations/index.js';
|
|
import { createAgentGroup, getAgentGroup } from '../src/db/agent-groups.js';
|
|
import {
|
|
createMessagingGroup,
|
|
createMessagingGroupAgent,
|
|
getMessagingGroup,
|
|
} from '../src/db/messaging-groups.js';
|
|
|
|
const db = initDb(path.join(DATA_DIR, 'v2.db'));
|
|
runMigrations(db);
|
|
|
|
const AGENT_GROUP_ID = 'ag-main';
|
|
const MESSAGING_GROUP_ID = 'mg-discord';
|
|
const CHANNEL_ID = 'discord:1470188214710046894:1491569326447132673';
|
|
|
|
// Agent group
|
|
if (!getAgentGroup(AGENT_GROUP_ID)) {
|
|
createAgentGroup({
|
|
id: AGENT_GROUP_ID,
|
|
name: 'Main',
|
|
folder: 'main',
|
|
agent_provider: 'claude',
|
|
created_at: new Date().toISOString(),
|
|
});
|
|
console.log('Created agent group:', AGENT_GROUP_ID);
|
|
} else {
|
|
console.log('Agent group already exists:', AGENT_GROUP_ID);
|
|
}
|
|
|
|
// Messaging group
|
|
if (!getMessagingGroup(MESSAGING_GROUP_ID)) {
|
|
createMessagingGroup({
|
|
id: MESSAGING_GROUP_ID,
|
|
channel_type: 'discord',
|
|
platform_id: CHANNEL_ID,
|
|
name: 'Discord Test',
|
|
is_group: 1,
|
|
unknown_sender_policy: 'strict',
|
|
created_at: new Date().toISOString(),
|
|
});
|
|
console.log('Created messaging group:', MESSAGING_GROUP_ID);
|
|
} else {
|
|
console.log('Messaging group already exists:', MESSAGING_GROUP_ID);
|
|
}
|
|
|
|
// Link
|
|
try {
|
|
createMessagingGroupAgent({
|
|
id: 'mga-discord',
|
|
messaging_group_id: MESSAGING_GROUP_ID,
|
|
agent_group_id: AGENT_GROUP_ID,
|
|
// Discord group channel → mention-sticky default. Mention once, stay
|
|
// subscribed to the thread. Admins can tune via /manage-channels.
|
|
engage_mode: 'mention-sticky',
|
|
engage_pattern: null,
|
|
sender_scope: 'all',
|
|
ignored_message_policy: 'drop',
|
|
session_mode: 'shared',
|
|
priority: 0,
|
|
created_at: new Date().toISOString(),
|
|
});
|
|
console.log('Created messaging_group_agent link');
|
|
} catch (err: any) {
|
|
if (err.message?.includes('UNIQUE')) {
|
|
console.log('Messaging group agent link already exists');
|
|
} else {
|
|
throw err;
|
|
}
|
|
}
|
|
|
|
console.log('Done! Run: pnpm run build && node dist/index.js');
|