@automagik/omni 2.260409.6 → 2.260421.3

package/db/drizzle/0018_supreme_puma.sql

@@ -0,0 +1,6 @@
+ALTER TABLE "instances" RENAME COLUMN "gupshup_api_key" TO "gupshup_callback_url";
+ALTER TABLE "instances" RENAME COLUMN "gupshup_app_name" TO "gupshup_auth_token";
+ALTER TABLE "instances" RENAME COLUMN "gupshup_source_phone" TO "gupshup_event_id";
+ALTER TABLE "instances" ALTER COLUMN "gupshup_callback_url" SET DATA TYPE text;
+ALTER TABLE "instances" ALTER COLUMN "gupshup_auth_token" SET DATA TYPE text;
+ALTER TABLE "instances" ALTER COLUMN "gupshup_event_id" SET DATA TYPE varchar(255);

package/db/drizzle/0019_idle_chat_follow_up.sql

@@ -0,0 +1,23 @@
+CREATE TABLE "chat_follow_up_state" (
+	"id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
+	"chat_id" uuid NOT NULL,
+	"instance_id" uuid NOT NULL,
+	"agent_id" uuid,
+	"sequence_config" jsonb NOT NULL,
+	"sequence_index" integer DEFAULT 0 NOT NULL,
+	"last_agent_message_at" timestamp with time zone NOT NULL,
+	"last_inbound_customer_message_at" timestamp with time zone,
+	"next_fire_at" timestamp with time zone,
+	"disarm_reason" varchar(32),
+	"disarmed_at" timestamp with time zone,
+	"created_at" timestamp with time zone DEFAULT now() NOT NULL,
+	"updated_at" timestamp with time zone DEFAULT now() NOT NULL
+);
+--> statement-breakpoint
+ALTER TABLE "chat_follow_up_state" ADD CONSTRAINT "chat_follow_up_state_chat_id_chats_id_fk" FOREIGN KEY ("chat_id") REFERENCES "public"."chats"("id") ON DELETE cascade ON UPDATE no action;--> statement-breakpoint
+ALTER TABLE "chat_follow_up_state" ADD CONSTRAINT "chat_follow_up_state_instance_id_instances_id_fk" FOREIGN KEY ("instance_id") REFERENCES "public"."instances"("id") ON DELETE cascade ON UPDATE no action;--> statement-breakpoint
+ALTER TABLE "chat_follow_up_state" ADD CONSTRAINT "chat_follow_up_state_agent_id_agents_id_fk" FOREIGN KEY ("agent_id") REFERENCES "public"."agents"("id") ON DELETE set null ON UPDATE no action;--> statement-breakpoint
+CREATE INDEX "chat_follow_up_state_sweeper_idx" ON "chat_follow_up_state" USING btree ("next_fire_at","disarm_reason");--> statement-breakpoint
+CREATE UNIQUE INDEX "chat_follow_up_state_chat_instance_unique" ON "chat_follow_up_state" USING btree ("chat_id","instance_id");--> statement-breakpoint
+CREATE INDEX "chat_follow_up_state_chat_idx" ON "chat_follow_up_state" USING btree ("chat_id");--> statement-breakpoint
+CREATE INDEX "chat_follow_up_state_instance_idx" ON "chat_follow_up_state" USING btree ("instance_id");

package/db/drizzle/0020_follow_up_config.sql

@@ -0,0 +1,2 @@
+ALTER TABLE "agents" ADD COLUMN "follow_up_config" jsonb;--> statement-breakpoint
+ALTER TABLE "instances" ADD COLUMN "follow_up_config" jsonb;

package/db/drizzle/0021_idle_follow_up_seed.sql

@@ -0,0 +1,51 @@
+-- Seed the default idle-chat follow-up automation.
+-- The follow-up sweeper publishes `chat.idle_timeout`; without an
+-- automation subscribed to that event, arming is a no-op in production.
+-- Source of truth for the structure lives at
+-- docs/examples/automations/idle-follow-up.yaml.
+
+INSERT INTO "automations" (
+  "id",
+  "name",
+  "description",
+  "trigger_event_type",
+  "trigger_conditions",
+  "condition_logic",
+  "actions",
+  "enabled",
+  "priority",
+  "created_at",
+  "updated_at"
+)
+SELECT
+  '00000000-0000-4000-8000-000000000f04'::uuid,
+  'Idle chat follow-up',
+  'Ask the agent to draft a follow-up when a customer goes idle after an agent reply. Paired with per-agent/per-instance follow-up config (see omni follow-up set ...).',
+  'chat.idle_timeout',
+  '[]'::jsonb,
+  'and',
+  '[
+    {
+      "type": "call_agent",
+      "config": {
+        "agentId": "{{payload.agentId}}",
+        "promptOverride": "The customer has been idle for {{minutes}} minutes since your last reply. This is follow-up #{{sequenceIndex}} in the sequence.\n\n{{syntheticPrompt}}\n\nWrite a short, warm follow-up message to {{chatName}} in their preferred language. Do not mention that this is an automated follow-up.",
+        "responseAs": "followUpReply"
+      }
+    },
+    {
+      "type": "send_message",
+      "config": {
+        "instanceId": "{{payload.instanceId}}",
+        "to": "{{payload.chatId}}",
+        "contentTemplate": "{{followUpReply}}"
+      }
+    }
+  ]'::jsonb,
+  true,
+  100,
+  NOW(),
+  NOW()
+WHERE NOT EXISTS (
+  SELECT 1 FROM "automations" WHERE "name" = 'Idle chat follow-up'
+);

package/db/drizzle/0022_idle_follow_up_prompt_v2.sql

@@ -0,0 +1,34 @@
+-- Upgrade the "Idle chat follow-up" automation promptOverride to use
+-- 1-based `{{attemptNumber}}` / `{{totalAttempts}}` placeholders instead of the
+-- zero-based `{{sequenceIndex}}`.
+--
+-- Context: in production the agent was reading "This is follow-up #0" and
+-- confusing itself into emitting meta-commentary ("_(limite atingido)_") from
+-- its own session memory. The new wrapper uses natural 1-based numbering and
+-- explicitly forbids stage directions / parenthetical notes.
+--
+-- Idempotent: only rewrites the built-in row. User-authored automations are
+-- untouched.
+
+UPDATE "automations"
+SET
+  "actions" = '[
+    {
+      "type": "call_agent",
+      "config": {
+        "agentId": "{{payload.agentId}}",
+        "promptOverride": "Follow-up context: attempt {{attemptNumber}} of {{totalAttempts}} — {{minutes}} minutes of silence since your last message to {{chatName}}.\n\n{{syntheticPrompt}}\n\nRespond with ONLY the customer-facing message. Plain text, no italics, no parentheses, no stage directions, no meta-commentary. Do not refer to yourself as an automation or follow-up bot.",
+        "responseAs": "followUpReply"
+      }
+    },
+    {
+      "type": "send_message",
+      "config": {
+        "instanceId": "{{payload.instanceId}}",
+        "to": "{{payload.chatId}}",
+        "contentTemplate": "{{followUpReply}}"
+      }
+    }
+  ]'::jsonb,
+  "updated_at" = NOW()
+WHERE "id" = '00000000-0000-4000-8000-000000000f04'::uuid;

package/db/drizzle/0023_dispatcher_inbound_age.sql

@@ -0,0 +1,8 @@
+-- Add `inbound_max_age_minutes` to `instances`. Drops inbound
+-- `message.received` events for the agent dispatcher when the platform-native
+-- timestamp (e.g. WhatsApp `messageTimestamp`) is older than this value.
+--
+-- Guards against history-sync replays and NATS redelivery of stale messages
+-- after reconnect/restart. Default: 10 minutes.
+
+ALTER TABLE "instances" ADD COLUMN "inbound_max_age_minutes" integer DEFAULT 10 NOT NULL;

package/db/drizzle/0024_quiet_gabe_jones.sql

@@ -0,0 +1,23 @@
+-- Add `handoff_logs` table to persist every agent→human handoff with full payload.
+-- Records instanceId, chatId, toPhone, text, extraInfo, agentId, and externalMessageId
+-- so handoffs can be queried, audited, and correlated with omni_events.
+
+CREATE TABLE "handoff_logs" (
+  "id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
+  "instance_id" uuid REFERENCES "instances"("id") ON DELETE SET NULL,
+  "chat_uuid" uuid REFERENCES "chats"("id") ON DELETE SET NULL,
+  "chat_id" varchar(255) NOT NULL,
+  "to_phone" varchar(100) NOT NULL,
+  "text" text NOT NULL,
+  "extra_info" text,
+  "agent_id" uuid REFERENCES "agents"("id") ON DELETE SET NULL,
+  "external_message_id" varchar(255),
+  "sent_at" timestamp DEFAULT now() NOT NULL,
+  "metadata" jsonb
+);
+
+CREATE INDEX "handoff_logs_instance_idx" ON "handoff_logs" ("instance_id");
+CREATE INDEX "handoff_logs_chat_uuid_idx" ON "handoff_logs" ("chat_uuid");
+CREATE INDEX "handoff_logs_chat_id_idx" ON "handoff_logs" ("chat_id");
+CREATE INDEX "handoff_logs_sent_at_idx" ON "handoff_logs" ("sent_at");
+CREATE INDEX "handoff_logs_agent_idx" ON "handoff_logs" ("agent_id");

package/db/drizzle/0025_panoramic_sinister_six.sql

@@ -0,0 +1,5 @@
+-- Add `handoff_fields` jsonb column to `handoff_logs`.
+-- Stores structured key-value pairs from the agent for Gupshup flow variable mapping
+-- (e.g. nome → var_global.name, temperatura_lead → var_global.calor_do_lead).
+
+ALTER TABLE "handoff_logs" ADD COLUMN "handoff_fields" jsonb;

package/db/drizzle/0026_agent_key_profiles.sql

@@ -0,0 +1,19 @@
+-- Omni scope profiles: add profile + allowlist columns to `api_keys`.
+--
+-- Existing keys are backfilled as follows:
+--   * `profile` stays NULL — they keep their hand-authored `scopes`
+--   * `profile_overrides` defaults to `'{}'::jsonb`
+--   * `chat_allowlist` / `instance_allowlist` / `outbound_recipient_allowlist`
+--     default to empty arrays. For NULL-profile keys the enforcer treats `[]`
+--     as "no lock" (backward compat). For profile keys that declare
+--     `requiresLocks`, `[]` means "deny all" — see docs/profiles.md.
+
+ALTER TABLE "api_keys" ADD COLUMN "profile" varchar(32);
+--> statement-breakpoint
+ALTER TABLE "api_keys" ADD COLUMN "profile_overrides" jsonb DEFAULT '{}'::jsonb NOT NULL;
+--> statement-breakpoint
+ALTER TABLE "api_keys" ADD COLUMN "chat_allowlist" text[] DEFAULT ARRAY[]::text[] NOT NULL;
+--> statement-breakpoint
+ALTER TABLE "api_keys" ADD COLUMN "instance_allowlist" uuid[] DEFAULT ARRAY[]::uuid[] NOT NULL;
+--> statement-breakpoint
+ALTER TABLE "api_keys" ADD COLUMN "outbound_recipient_allowlist" text[] DEFAULT ARRAY[]::text[] NOT NULL;

package/db/drizzle/0027_bridge_tmux_session.sql

@@ -0,0 +1,13 @@
+-- Per-instance bridge tmux session override for the genie `nats-genie` provider.
+--
+-- When set, the provider propagates this value via the NATS message env as
+-- `GENIE_TMUX_SESSION`; the consumer genie bridge uses it as the highest-
+-- priority override in its three-layer tmux-session resolution chain.
+-- NULL keeps today's behavior (no override, genie falls back to agent-level
+-- or name-based defaults).
+--
+-- Enables one-agent-many-instances fan-out — e.g. a single "scout" agent
+-- hooked to N inbound numbers lands each instance's dispatches in its own
+-- tmux session for isolation and live-intelligence observability.
+
+ALTER TABLE "instances" ADD COLUMN "bridge_tmux_session" text;