agents_control 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b71d165050803893091b3bce0857cb4a9cac7875e28289e0aaebc6bf4a1aa820
-  data.tar.gz: a301e0e972625e0eb57a79e80799e21edf2232d24ef8bbbfb74840484d1feb7e
+  metadata.gz: 5ca83918e01b4dc98c7b72f17da5cd31d859d863d61614f7eee74dd01e62ecb2
+  data.tar.gz: d50f30441533aded38f243800dda29a884fd01fda135506dee034115eeb63e7a
 SHA512:
-  metadata.gz: b6a5dd4eb521026c1084ade954fbe7d7a8f26426e3d68d78077a3d69e71addc0c40165181eaaff963a225434a71167e0ed02f68382fe8ed4605a46f8e781bc54
-  data.tar.gz: 7077e2aa298e86630f4c619e67a6bde0be85a2316f86c43b46dbd354353bc9404f91a0db8aa86ab9f8fcf1f0c3d6e8cee101c1b55cbf53080810f52d2ba37df1
+  metadata.gz: 9dd870ff93dd579dd1bbbc7cffd7e9f62d7a5d25ba79d2f69adb6018ac1ae8061614b5e1d09db5bc817d65f8f6a33fc7557b8a6a035245d640e92373bcdc598d
+  data.tar.gz: 71c5a463b794b2196fa3023a0a703ab6cd02da596f2b1f003ea1365db96f9a67e8d3ab3e1ddc51bdd470d76217395907565a2d53ef65dccf6fc0b411c04dee0a

data/README.md

@@ -104,20 +104,27 @@ Bot commands:
 
 The number `N` comes from the last list shown.
 
-`/run` treats the command itself as the reference point: the shell
-echoes back whatever's typed, so it looks for that exact text on
-screen and shows from there — sharper than diffing screenshots, and
-it still works even if something else wrote to the same tab in
-between, since it doesn't need the screen from right before typing to
-relate to the screen after at all. A short reply ("y", "n" mid `git
-add -p`) isn't a safe anchor on its own — too likely to match
-something unrelated — so those fall back to a before/after diff
-instead, and when even that can't cleanly tell what's new, to the
-current screen outright: seeing the result, possibly with a little
-stale context around it, beats not seeing it at all. How much gets
-captured either way is a `/settings` option (`terminal.run_result_lines`,
-200 by default) — a command whose output runs longer just gets its
-last N lines, same as the default gets cut by a screen that's too tall.
+Against a plain tab, `/run` treats the command itself as the reference
+point: the shell echoes back whatever's typed, so it looks for that
+exact text on screen and shows from there — sharper than diffing
+screenshots, and it still works even if something else wrote to the
+same tab in between, since it doesn't need the screen from right
+before typing to relate to the screen after at all. A short reply
+("y", "n" mid `git add -p`) isn't a safe anchor on its own — too
+likely to match something unrelated — so those fall back to a
+before/after diff instead, and when even that can't cleanly tell
+what's new, to the current screen outright: seeing the result,
+possibly with a little stale context around it, beats not seeing it
+at all. How much gets captured either way is a `/settings` option
+(`terminal.run_result_lines`, 200 by default) — a command whose output
+runs longer just gets its last N lines, same as the default gets cut
+by a screen that's too tall.
+
+Against an agent, `/run` just confirms the send — an agent isn't a
+shell command that finishes in a couple of seconds, so there's no
+"result" to capture yet by the time it would look. Hooks already own
+telling Telegram when it's actually done or needs something, the same
+as replying to one of its own questions.
 
 The result stays a live target: replying to it — "y", "n", anything —
 types straight into that same pane and shows what came back, so

data/lib/agents_control/channels/telegram/router.rb

@@ -200,7 +200,15 @@ module AgentsControl
             if remote?(session)
               confirm_remote(chat_id, session, command)
             else
-              execute(chat_id, session, command, show_result: true)
+              # An agent isn't a shell command that finishes in a
+              # couple of seconds — it's a real task, and hooks already
+              # own telling Telegram when it's actually done or needs
+              # something. Capturing a "result" a moment after typing
+              # would just catch it mid-thought and fall back to
+              # dumping its whole transcript, which isn't a result at
+              # all — same reasoning as replying to an agent's own
+              # question (type_into_session).
+              execute(chat_id, session, command, show_result: !session.agent?)
             end
           end
         end
@@ -514,7 +522,7 @@ module AgentsControl
           case payload["action"]
           when "focus" then focus_session(chat_id, session)
           when "screen" then show_screen(chat_id, session)
-          when "run" then execute(chat_id, session, payload["text"], show_result: true)
+          when "run" then execute(chat_id, session, payload["text"], show_result: !session.agent?)
           when "close_confirm" then say(chat_id, "Close #{session.label}?",
                                         markup: @keyboards.confirm("close", session))
           when "close" then close_session(chat_id, session)

data/lib/agents_control/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module AgentsControl
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: agents_control
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Sapar Kurmanov