brainiac-discord 0.0.18 → 0.0.20

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 81f74969c95690e118d85fe590b2e2d35b39609937e807afaa2865ac58c8846d
-  data.tar.gz: cde31da7b3a0b2a4b84bff28b4b1e2fa99fe6ba7e7e8e372b572b1d0ea085c5c
+  metadata.gz: 173d9471b14272a611b844fb7a12e0d728f812ab2b06cda08b05faf26329243c
+  data.tar.gz: c0658fe873c620e9b1be027d1866035b4d6bd846e13088626eefa174e77c186d
 SHA512:
-  metadata.gz: 397af906d3f427dab7723fe20d3cc25840a35e109e4e054f9cf9689337cbcc8ccc376e0b14403d5dd38ede9fc25b3b2e2efa368371dae012b14c6dd5e9f0aa03
-  data.tar.gz: 8201ec6515468a4ed1a1f4e63ecc8bdf66c57e333a096c00c216559bb4a1466443928ea6c35542efdd77f80bea0c80a2555916cf053ffff41e6e721f329029ba
+  metadata.gz: d3997e24550bd3be11cb48942dafa1b624cdc0288410ce5388e4eca6a5145f61291d7dce56295c34544c9dad46407572c3b587e96b3c35a2c168ea4a34afa09e
+  data.tar.gz: 55a5b86aae6ce19a9d37b2e2e2d438d3c7ddc80c166367996ffaa9f1355a98613e2f10cb0582c4e171e8e135b27b507cee5317731173a8e01bec63ff795de870

data/lib/brainiac/plugins/discord/message.rb

@@ -1312,6 +1312,13 @@ module Brainiac
                 exit_status: exit_status, profile: profile
               )
 
+              # Capture and store the CLI session id for future --resume-id dispatches.
+              # This allows resuming the specific session for this worktree rather than
+              # whichever session was globally last. The session id gets stored on the
+              # work item (keyed by agent_cli and worktree), and cli_session_id_for will
+              # retrieve it when resolve_resume is called.
+              capture_discord_session_id(resolved: resolved, work_dir: work_dir, agent_name: agent_name)
+
               if exit_status.signaled? || session_cancelled
                 handle_cancelled(exit_status, session_cancelled, agent_name, message_id,
                                  response_file, meta_file, prompt_file, attachment_paths)
@@ -1380,6 +1387,25 @@ module Brainiac
             LOG.warn "[Discord:#{agent_name}] Failed to archive session history: #{e.message}" if defined?(LOG)
           end
 
+          # Capture and store the CLI session id after a Discord dispatch completes.
+          #
+          # Discord threads get worktrees registered as work items (via register_work_item
+          # in create_thread_worktree), so we can use the core's capture_cli_session_id
+          # to store the session id on the work item. On future dispatches, resolve_resume
+          # calls cli_session_id_for which retrieves this stored id, enabling accurate
+          # --resume-id targeting instead of resuming whichever session was globally last.
+          #
+          # Fully best-effort: capture_cli_session_id already logs failures internally,
+          # but we guard here too so a session capture failure never breaks Discord's flow.
+          def capture_discord_session_id(resolved:, work_dir:, agent_name:)
+            return unless defined?(capture_cli_session_id)
+            return unless resolved && work_dir
+
+            capture_cli_session_id(resolved: resolved, chdir: work_dir)
+          rescue StandardError => e
+            LOG.warn "[Discord:#{agent_name}] Failed to capture session id: #{e.message}" if defined?(LOG)
+          end
+
           def handle_completed(exit_status:, agent_name:, agent_config_name:, channel_id:, message_id:,
                                bot_token:, response_file:, meta_file:, log_file:,
                                project_config:, head_before:, status_before:)

data/lib/brainiac/plugins/discord/prompts.rb

@@ -11,6 +11,12 @@ module Brainiac
         CHANNEL = <<~PROMPT
           ## Discord Channel Rules
 
+          ### Current Message Priority
+          The message in "**Message:**" above is your PRIMARY task. Everything else is context.
+          - Original thread topic: reference only — don't answer questions that weren't asked
+          - Channel history: context only — helps you understand the conversation flow
+          - Your job: respond to the current message, not summarize the thread
+
           ### Mentions
           Discord does NOT support plain-text @mentions. Writing `@Galen` renders as plain text.
           To actually mention someone, use the `<@USER_ID>` format. Here are the known IDs:

data/lib/brainiac/plugins/discord/version.rb

@@ -3,7 +3,7 @@
 module Brainiac
   module Plugins
     module Discord
-      VERSION = "0.0.18"
+      VERSION = "0.0.20"
     end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: brainiac-discord
 version: !ruby/object:Gem::Version
-  version: 0.0.18
+  version: 0.0.20
 platform: ruby
 authors:
 - Andy Davis