After restarting your Mac, for example, opening an app you created sometimes did nothing.
This happened because Kagemusha mistakenly judged that the app was still running.
Kagemusha now confirms that the app is actually running before making that judgment.
We have also added "Send Your Situation to Support" to the Kagemusha screen in the sidebar.
If something is not working, such as an app that does not open, describe what is happening and click Send.
Kagemusha attaches information that helps us find the cause, such as its version, the location of Chrome, and the app launch log.
Open pages and sign-in information are not sent.
You can review what will be sent on screen before sending.
This release also includes two improvements:
Settings in the menu bar now shows the Kagemusha window even when it is closed.
The confirmation shown when you create an app with an existing name no longer hides behind other windows.
On a Mac without the Xcode Command Line Tools, creating an app failed with a "No developer tools were found" error.
This happened because Kagemusha built parts of each app on that Mac every time you created one.
Kagemusha now ships with these parts prebuilt and uses them when it creates an app.
You do not need to install any developer tools.
This works the same on Intel and Apple silicon Macs.
We apologize for the inconvenience.
If you could not create an app because of this error, please update Kagemusha to 1.4.3 and try again.
This release also includes two improvements:
When an AI agent launches an app in the background, its window no longer flashes to the front.
The AI skill now waits 20 to 45 seconds between page navigations on the same site.
On a Mac user account without administrator rights, creating an app could fail with a "permission denied" error.
This happened because only administrators can write to the Applications folder.
Kagemusha now creates the app in the Applications folder inside your home folder when it cannot write to the Applications folder.
Apps created there open from Spotlight and Launchpad as well.
If you have chosen a different location in Settings, Kagemusha keeps creating apps there as before.
We have also updated the icon of the built-in Buffer preset.
When one app keeps CPU usage at 50% or more for over 5 minutes, you are now notified with the app's name.
If a page left open keeps using the CPU and your whole Mac slows down, you can see at once which app is the cause.
For apps with "Allow AI control" turned on, the notification also shows the name of the heaviest page.
From the notification's buttons, you can reload that page or switch it to a blank page.
You can turn these notifications on or off with "Notify when an app keeps using the CPU" in Settings (on by default).
New apps now start with "Allow AI control" turned off.
When you turn it on, a confirmation appears.
It asks you to check the terms of the service the app will operate, and not to use AI control on services that prohibit automated operation.
Apps you already let AI operate keep their current setting.
From "AI Integration" in Settings, you can now add one extension to Claude Desktop and operate your Kagemusha apps from it.
There is no configuration file to edit.
You can now register Chrome Web Store extensions in Kagemusha and add just the ones you need to any app, including apps you have already created.
"AI integration" now lists each AI agent found on this Mac, and you can install, update or remove the skill for each one. When an existing skill is replaced, the original files are kept as a backup.
Also fixed the update notice overlapping buttons on the Dock screen.
Apps you create now keep drawing pages and running timers while their windows are hidden or minimized. Services that show clocks or notifications keep working correctly.
Google Chrome and Chrome Canary have removed the mechanism that loads extensions passed from outside the browser.
Because of that, when you open a Chrome-based app straight from the Dock or Spotlight, Space mode, window handling, URL rules and the Dock notification badge have no effect.
The settings screen and the create screen now say which of those settings will not work.
To use them, pick Brave, Chromium, Edge, Vivaldi or Opera as the browser.