Repository navigation
Releases: promptclickrun/bighelp-plugin
Release list
bighelp plugin 3.17.0
3.17.0: alerts for messages between agents
This release lets the phone get an alert when one agent sends a message to another agent.
In this release
- Alerts for messages between agents (#165): an agent on this computer can send a message to another agent. An example is the answer to work that the other agent gave it. Phones with Peer chats on get an alert for this message.
- The alert shows the name and the picture of the agent that wrote the message.
- The alert opens the chat of the agent that got the message.
- Each message gives one alert.
The bighelp app shows this switch as "Agents messaging each other" in 2.5.1 (133) and later. Older apps show it as "Peer chats". It works the same.
Tested
- The new test in
test_managed_notificationspasses. The other results in that file are the same as onmain. - The three version strings are 3.17.0. The release workflow checks that they match.
hermes plugins doctor . --cipasses with the same warnings as 3.16.0.- Not tested on a real host.
Made by Claude Opus 5.5 (claude-opus-5-5) in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.16.0
3.16.0: teamwork that leads, busy chats, names on newer Hermes
This release makes Teamwork stronger and fixes agent names on Hermes 0.22 and later. The bighelp app can also show and stop a chat that another Hermes process runs.
In this release
- Agent names on newer Hermes (#161): Hermes 0.22 and later ship ruamel.yaml, not PyYAML. Alerts and the Teamwork brief now use the agent's name, plugin self-updates no longer stop at the capability check, and skill names read again.
- Teamwork leads (#162): each agent now hands work to the teammate whose role fits, without being told. Chats that were open before Teamwork get the brief once, as a note that Hermes keeps with the message.
- A chat busy in another process (#163): the new feature
native-chat-activity-v1. The app can see that another Hermes process runs a chat (for example an agent that another agent asked), show it as busy, and stop it. Stop sends that process Ctrl-C, only when its pid and start time match the Hermes lease for that chat.
You need bighelp 2.5.0 (129) or later to see a busy chat and stop it. Older apps work as before.
Tested
test_team,test_chat_activity,test_adapter,test_plugin_update_executionandtest_plugin_update_launchdpass on Hermesmain(2026-10-18).- The full suite has fewer failures than 3.15.0. No new test fails.
- The Hermes plugin scan gives
safe.
Made by Claude Opus 5.5 (claude-opus-5-5) in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.15.0
3.15.0: agents that know each other
This release lets agents on one computer know each other and ask each other for help. It also lets the bighelp app show what an agent does when another agent asks it something.
In this release
- Agents talking (#157): the new feature
native-agent-talk-v1, with the read-only routeagents/talk.- When one agent asks another agent, the app shows what the other agent does now, for example "Nova is searching the web".
- The route reads the history of the other agent, read-only. The app sends a hash of each message, never the words. The plugin stores nothing.
- Teamwork (#158): the new feature
native-team-v1, with the routeteam. It is off until you turn it on in the app.- When it is on, each agent gets a short brief in bighelp chats.
- The brief has the name and role of each other agent, and how to ask them for help.
- The plugin writes the brief into the Hermes setting
platform_hints.bighelp.appendof each agent. Text that you wrote in that setting stays. When you turn Teamwork off, the plugin removes its text.
- Safer feature checks (#159): if Hermes is in an unusual state, the app does not show the two new features. All other features continue to work.
You need bighelp 2.5.0 (128) or later for Teamwork and the live status of the other agent. Older apps work as before.
Tested
tests/test_team.pyandtests/test_agent_talk.pypass on Hermesmain(2026-10-18).- A test saves the Teamwork brief through the Hermes config helpers in a throwaway Hermes home. Then it reads the brief back as Hermes does when it builds a prompt.
- On a throwaway Hermes host, the
agents/talkroute showed the tool that the other agent ran, and then "not working" after the answer. - The full suite has the same failures as 3.14.0. This release does not cause them.
Made by Claude Opus 5.5 (claude-opus-5-5) in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.14.0
3.14.0: Composio for your agent
This release lets the bighelp app turn on Composio for an agent.
In this release
- Composio for your agent (#154): the new feature
native-composio-v1, with two routes.composio/statustells which Composio MCP servers the agent's Hermes settings have, if they are on, and if Hermes has a sign-in for them.composio/installadds Composio Connect (https://connect.composio.dev/mcp, OAuth) or turns it on. Hermes' own MCP sign-in then signs it in to the user's Composio account.- The plugin never sees a Composio credential. Hermes keeps its own tokens.
You need bighelp 2.5.0 (125) or later for Settings › Apps › Composio Apps. Older apps work as before.
Tested
tests/test_composio.py: 25 tests pass on Hermes 0.22.2 and 0.21.2.- The full suite has the same failures as
main. This release does not cause them.
Made by Claude Opus 5.5 (claude-opus-5-5) in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.13.0
3.13.0: group chat typing, agents on other computers, app appearance tool
This release shows which agent types in a group chat, also for agents on other computers. It also lets an agent change how the bighelp app looks.
In this release
- "Is typing" in group chats (#151): the new feature
native-room-typing-v1. A room feed can tell which member writes now. The event has no message text and no reasoning text. - Room activity works on real hosts (#152): before, a real dashboard never listed
native-room-activity-v1, because Hermes loads the plugin two times. Now the plugin keeps one shared state. Each Hermes process writes short notes (only IDs and a time, never text) toplugin-data/loopdy/room-presence.sqlite3. The plugin deletes them after 30 seconds. - Agents on other computers (#152): the new feature
native-room-peer-typing-v1. When an agent on this computer is a member of a group chat on another computer, the app can see when it types. - Agents can change how bighelp looks (#150): the new iPhone tool
iphone_appearance(featurenative-device-appearance-v1). It reads or sets light or dark mode and the app color.
You need bighelp 2.5.0 (124) or later to see "is typing" names and group chats with agents on other computers. Older apps work as before.
Tested
- The room activity, room presence and native context tests pass.
- Two isolated Hermes hosts on one Mac, with a group chat across them (
Scripts/RoomLinkProbe.pyin the app repo): the app showed "is typing" for the agents on both computers. - Three tests fail the same way on
main. This release does not cause them.
Made by Claude Opus 5.5 (claude-opus-5-5) in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.12.0
3.12.0: Dev Factory, coding workflows across git projects
This release adds Dev Factory for Bighelp IDE. A recipe runs the same coding job in several git projects. Each run uses its own worktree, can run your tests, waits for you to approve the changes, and can open a pull request.
In this release
- Dev Factory (#148): workflows with
"schemaVersion": 3. Version 1 and 2 workflows work as before. The contract is indocs/DEV_FACTORY.md.- A recipe lists 1 to 10 git projects. One start makes one run per project.
- Each run gets a new worktree in
<repo>/.worktrees/, or uses the project folder. The plugin never removes a worktree. - Command steps run a command, for example your tests, without a shell and with a time limit. Hermes' keys and your AI providers' keys never reach the command.
- A run can wait for you to approve its changes. If the folder changes after you looked, the plugin refuses the approval.
- Pull request steps use your own git and GitHub CLI sign-ins.
- The feature is
native-workflows-code-v1. The plugin lists it whengitis on the computer'sPATH.
You need bighelp 2.3.0 (118) or later for Dev Factory (☰ › Dev Factory in Bighelp IDE). Older apps do not see the new recipes.
Tested
tests/test_workflow_code.pyandtests/test_workflow_code_model.py: 31 tests pass. They use throwaway git repositories and a stand-ingh.tests/test_portability.py: the version check passes (the version is the same in all files). One other portability test needs Hermes installed (gateway), so it cannot run on this machine. It fails the same way onmain.
Made by Claude Opus 5.5 (claude-opus-5-5) in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.11.4
3.11.4: notifications work on hosts whose notification folder was readable by others
Notification setup now works on hosts where the notification folder of the plugin was readable by other users. Before, the bighelp app showed "Couldn't confirm setup" on these hosts, often VMs.
In this release
- Notifications work on more hosts (#146): the plugin keeps its notification key in
plugin-data/loopdy/managed-notifications. Only the Hermes user can open this folder (700). An install script, a copy or a volume can make this folder 755. When the Hermes user owns the folder, the plugin now makes it private and continues. The plugin still refuses a link, a folder of another user, and a key file that other users can read.
You do not need an app update. After the update, use Set Up Again for the computer in the notification settings of bighelp.
Tested
tests/test_managed_notifications.py: a new test makes a 755 folder private and starts the service. A link in place of the folder is still refused. Without the fix, the test fails. The four notification test files pass with Hermesmain: 62 tests.tests/test_portability.py: the version check passes (the version is the same in all files). One other portability test needs Hermes installed (gateway), so it cannot run on this machine. It fails the same way onmain.
Changes made with Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.11.3
3.11.3: chats work right after an in-app Hermes restart
After the bighelp app updates this plugin and restarts Hermes, chats that were open before the restart now accept messages immediately. Before, the next message in such a chat could fail with "This chat is open in another Hermes process" for up to five minutes.
In this release
- Chats work right after an in-app restart (#143): the app restarts Hermes in place, with the same process ID. Hermes thus kept the chat locks of the old process. When Hermes starts, the plugin now removes these locks. This also applies to the restart that installs this version.
You do not need an app update.
Tested
tests/test_host_restart.pywith the real Hermes lock registry (Hermes 0.21.2 and Hermesmain): before the fix, the test fails with the same refusal as on a host. With the fix, it passes. The full suite has the same 11 failures as onmain, in other modules.tests/test_portability.py: the version check passes (the version is the same in all files). One other portability test needs Hermes installed (gateway), so it cannot run on this machine. It fails the same way onmain.
Changes made with Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.11.2
3.11.2: Codex credits show as credits, not dollars
The Usage screen in the bighelp app now shows a Codex credits balance as credits. Before, 14,000 credits showed as "$14,000.00".
In this release
- Codex credits are credits (#140): the Codex
Creditsfact is now a count, for example "14,000 credits" or "4.5 credits". Balances that are money (OpenRouter, Nous Portal) do not change.
No app update is needed. The app shows the value as the plugin sends it.
Tested
tests/test_provider_usage.py: the Codex tests pass, and a new test checks a balance of 14,000 credits.tests/test_portability.py: the version check passes (the version is the same in all files). One other portability test needs Hermes installed (gateway), so it cannot run on this machine. It fails the same way onmain.
Changes made with Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code
bighelp plugin 3.11.1
3.11.1: agents keep workflows as drafts and publish only when asked
Agents now keep the workflows that they build for you as drafts. An agent publishes a workflow only when you tell it to publish the workflow or to make it live, and you approve that. In the bighelp app, a draft shows a Publish button.
In this release
- Workflows stay drafts (#138): the
bighelp_workflowstool and the bighelp chat brief tell agents to publish only when you explicitly ask. Publish still asks you to approve, as your computer's approval settings say.
No app update is needed for this rule. bighelp build 92 adds a Publish button and default values for workflow inputs.
Tested
- 1 new test. The agent guide, workflow and tool registration tests pass (33 tests).
🤖 Generated with Claude Code