7ad9ace2cc
The pane, in-app browser, and reaction tools were gated on HERMES_DESKTOP=1 — an env var set only on backends Electron spawns itself (local and SSH). A desktop client connected to a plain URL gateway or Hermes Cloud lost all six: they were stripped from the schema before the model saw them, on the same backend whose platform hint was telling it "you are chatting inside the Hermes desktop app". open_preview, read_preview, read_terminal, close_terminal, focus_pane, and react_to_message were all silently absent. The client is not the host. Capability now resolves from the session's own source, which session.create already carries: - The six tools move into a `desktop_ui` toolset, off _HERMES_CORE_TOOLS so no other platform pays their schema. - _gui_surface_toolsets(platform) folds `desktop_ui` (and the existing `project` tools) into the GUI gateway's resolution when the session's platform is the desktop app — the same answer on every topology. - check_fn drops the env probe. It kept the one thing that is genuinely a per-process/user fact: react_to_message's display.message_reactions opt-in, which the desktop mirrors onto whichever gateway it is connected to. react_to_message was doubly broken: it read that toggle behind the env gate, so even a local-backend user's Settings toggle could not reach a remote session. The embedded terminal pane keeps working correctly the other way round: it runs `hermes --tui` against a desktop-spawned backend, and a tui-sourced session gets no GUI tools even though HERMES_DESKTOP=1 is set on that process.
63 lines
2.4 KiB
Python
63 lines
2.4 KiB
Python
#!/usr/bin/env python3
|
|
"""Close a read-only agent terminal tab in the Hermes desktop GUI.
|
|
|
|
Each ``terminal(background=true)`` process is mirrored as a read-only tab in the
|
|
desktop's terminal pane. This tool lets the agent drop a tab it no longer needs
|
|
to show — WITHOUT killing the process (use ``process(action='kill')`` for that).
|
|
The output keeps buffering and the user can reopen the tab from the status stack.
|
|
|
|
It routes through the process registry's ``on_close`` sink, which the desktop
|
|
gateway wires to emit a ``terminal.close`` event the renderer handles. Like
|
|
``read_terminal`` it lives in the ``desktop_ui`` toolset, which the GUI gateway
|
|
enables only for desktop-sourced sessions, so it never appears outside the GUI.
|
|
"""
|
|
|
|
import json
|
|
|
|
from tools.process_registry import process_registry
|
|
from tools.registry import registry, tool_error
|
|
|
|
|
|
def close_terminal_tool(process_id: str) -> str:
|
|
"""Ask the desktop GUI to close a background process's read-only tab."""
|
|
pid = (process_id or "").strip()
|
|
if not pid:
|
|
return tool_error("process_id is required (the background process whose tab to close).")
|
|
|
|
return json.dumps(process_registry.request_close_terminal(pid), ensure_ascii=False)
|
|
|
|
|
|
CLOSE_TERMINAL_SCHEMA = {
|
|
"name": "close_terminal",
|
|
"description": (
|
|
"Close the read-only terminal tab for one of your background processes in "
|
|
"the Hermes desktop GUI (the tabs mirroring terminal(background=true) runs). "
|
|
"This does NOT kill the process — it only drops the tab/view; the output "
|
|
"keeps buffering and the user can reopen it from the status stack. Use it "
|
|
"to tidy up when a background process's live terminal is no longer worth "
|
|
"showing. To actually stop the process, use process(action='kill') instead."
|
|
),
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"process_id": {
|
|
"type": "string",
|
|
"description": (
|
|
"The background process's session id (from terminal(background=true) "
|
|
"output or process(action='list')) whose tab should be closed."
|
|
),
|
|
},
|
|
},
|
|
"required": ["process_id"],
|
|
},
|
|
}
|
|
|
|
|
|
registry.register(
|
|
name="close_terminal",
|
|
toolset="desktop_ui",
|
|
schema=CLOSE_TERMINAL_SCHEMA,
|
|
handler=lambda args, **kw: close_terminal_tool(process_id=args.get("process_id", "")),
|
|
emoji="🖥️",
|
|
)
|