Electra One Editor

Your projects are files, in a folder you chose.

Every project, revision and Lua script is written as a JSON file into a library folder you choose. Files can be backed up, copied to other computers or shared with other users. No magic or hidden traps here. The same folder holds a CLAUDE.md you write in the app — how you like Lua, which controller is on the desk, what to leave alone — and both agents are handed it: the assistant built into the editor with every question, and a Claude Code session opened on your watched slot folder before it writes a line.

Your Anthropic API key is kept safe in the system keychain. No account sits behind any of it. The key is yours, billed to your own Anthropic account, and it never leaves the machine.

One prompt. A working arpeggiator, checked on the device.

The whole session was one message: hold notes from a source you pick by interface, port and channel; send them to a destination picked the same way; put that routing on its own Config page; and give the first page two knobs, tempo and pattern, with the common arp patterns. The assistant wrote main.lua, uploaded it, read the controller’s log, wrote four tests, found and patched a missing default on its own, re-uploaded and confirmed the log was clean — without being asked again.

Total cost for that session: $0.968, on Sonnet 5. One prompt, fully working, verified on real hardware rather than hoped to be right.

A slot in the controller, as a folder on your disk.

Point the slot you are working on at a folder and the preset becomes an ordinary directory of files: keep it in Git, open it in VS Code, let Claude Code rewrite it. A change on disk is staged in the slot browser and waits for Apply changes, so nothing reaches the hardware until you say so.

The app writes nothing into the folder except what is under .electra/: the result of a request, the controller’s log, the MIDI traffic and, when asked, a picture of its screen — which is how an agent sees what it just did.

Ctrl+Shift+B puts the preset on the hardware.

Simple, yet effective. Once a slot is watching a folder, the extension makes that folder an ordinary VS Code project and uploading it to the controller is a standard build task. One keystroke saves your open editors, writes every changed file to the slot, reloads the preset on the controller and runs the preset’s tests.

Three more tasks have shortcuts of their own:

• Reload the preset without writing anything.
• Run the tests alone.
• Photograph the controller’s screen into the folder, so you can see what it actually drew.

The status bar says which preset the slot is running, and the controller’s log is printed after every upload.

Offline is a choice, not a limit.

One click signs the app into your Electra One account and the shared preset library opens inside it — presets published by other users to search, open and import, and your own to upload and share back. Download a preset once and it is on your disk like everything else.

Go offline again when you want to quit the online mode.