AIObox Desktop 0.2: multiple Claude accounts and custom providers
AIObox Desktop 0.2.0 and 0.2.1 run multiple Chrome profiles in parallel, widen the Claude chat column, add custom AI providers, a NewTab, and AkiMCP control inside the app.
Two releases, 0.2.0 (Aug 26) and 0.2.1 (Aug 28), of the AIObox desktop app aim at one goal: use several AI accounts at once without sessions bleeding into each other. Highlights include a wider Claude chat column, custom AI providers, a blank NewTab with a real address bar, and an AkiMCP control cluster at the top of the app.
Is running multiple Claude accounts in parallel safe?
Each Chrome profile is cloned and opened simultaneously with its own DevTools port, keeping an independent cookie jar — so the two accounts never share a session. AIObox also widens the Claude column: a per-profile Widen Claude flag plus an Inject all button applied to every open window, stripping the max-w-[50.5rem] width limit and re-applying it whenever Claude remounts its UI.
Custom providers and the NewTab
Enter any URL to add a custom provider; AIObox fetches the site icon into ~/.aki/aiobox/providerIcons/, and hovering shows an × to remove it. Gemini now opens like every other provider (the "Planned" lock is gone). A blank NewTab with a normal address bar opens any page outside the preset list.
AkiMCP and the dev-machine installer
The top of the app carries an icon-only AkiMCP cluster: setup, run, stop; the core auto-starts when a connection is already saved. Version 0.2.1 collapses the overlay z-index scale into one ladder — dropdown < backdrop < topbar < sidebar < modal < toast — and adds scripts/install-desktop.sh to build the arm64 .app, re-sign it as "AIObox Dev", and drop it straight into /Applications.
install-desktop.sh is dev and test only, so TCC grants survive each rebuild — it is not the official GitHub Release path.
The desktop app ships on its own release cadence, split from the AIObox web surface. The Postman toolchain above pairs directly with aki-mcp-sv 1.15.