| 1234567891011121314151617181920 |
- name: jp-kokkai
- repo: https://github.com/TakeshiTGAL/hermes-plugin-kokkai
- sha: 0c9bcfc49f64fd063131bf2676904f2ea166002c
- description: "Each watch run costs 0 tokens, and the unmanned run holds no tools. Posts new Diet meeting hits as metadata and the official meeting URL, with kokkai_search, kokkai_speech, and kokkai_watch. Disclosure — Talks only to kokkai.ndl.go.jp over HTTPS GET with no API key. kokkai_speech requests speech text and returns a short excerpt. Speech text is not stored. The tools are on for every surface, including gateways, and the plugin has no user list of its own: anyone you allow on your Hermes gateway, and a guest in a room with an empty allowlist, can search, read a speech excerpt, add a watch and approve it. Turn a surface off with hermes tools. kokkai_watch add writes HERMES_HOME/scripts/jp-kokkai-watch.py and creates one cron job that does not call a model, once a day, at the hour you pick in Hermes's own timezone. Each run costs 0 tokens and has no daily cap. Empty script output sends nothing. The job and the script stay after uninstall until you run hermes cron remove, with -p and the profile name when the profile is not default. Adding or removing a watch returns one pre_tool_call approve line, as does a repeat add that switches the saved job. Hermes shows it. An unchanged repeat add returns none. yolo and approvals off skip the prompt when a person is present. A cron job, hermes -q, and a separate plugin process cannot add or remove a watch even after always. A webhook or API-server turn inside the gateway is refused by Hermes unless \"always\" was already given for that exact add plan. plugins.isolation: host still blocks add and remove. Answering \"always\" on add covers only the same add plan. That choice adds one plugin_rule:kokkai_watch: line to config.yaml, and the line stays after the plugin is removed. A different add plan asks again. Remove builds a new rule key on every call, so answering always on remove does not cover the next remove, including the call that deletes the cron job. While the read-meetings skill is enabled, Hermes adds one line to the skill index of every session, including a session whose tools are turned off. The scheduled script does not run inside plugins.isolation: host, so that setting does not stop the watch. kokkai_watch run still cannot save seen speech IDs under plugins.isolation: host and says so on every run of the tool. The cron mark is cron.execution_identity.current_cron_execution (Hermes 0.21.6). The daily job is created with the public hermes cron command using --no-agent and --script. hermes cron create on 0.21.6 cannot pin a toolset, which does not matter because the unmanned run holds no tools. Running add again asks, then switches a model job onto the script and clears its prompt. A job made by 0.1.x keeps its model turn until the next add. An update can stop the watch if the cron mark or that command moves. Each request waits up to 30 seconds for data. The script timeout is 3600 seconds unless it was changed. State (your watch words, seen speech IDs and the job id) stays in plugin-data/jp-kokkai after uninstall. Tested with a stand-in server on Hermes 0.22.2, not in a live chat."
- maintainer: TakeshiTGAL
- tier: community
- category: tools
- requires_hermes: '>=0.21.6'
- docs_url: https://github.com/TakeshiTGAL/hermes-plugin-kokkai#readme
- version: "0.2.4"
- image: https://raw.githubusercontent.com/TakeshiTGAL/hermes-plugin-kokkai/0c9bcfc49f64fd063131bf2676904f2ea166002c/assets/catalog-banner.png
- platforms: []
- capabilities:
- provides_tools:
- - kokkai_search
- - kokkai_speech
- - kokkai_watch
- provides_hooks:
- - pre_tool_call
- provides_middleware: []
|