GitHub - zenbu-labs/zenbu.js: The framework for building hackable software · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
zenbu-labs
zenbu.js
Public
Notifications<br>You must be signed in to change notification settings
Fork<br>10
Star<br>216
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>264 Commits<br>264 Commits
.github/workflows
.github/workflows
assets
assets
packages
packages
scripts
scripts
.gitignore
.gitignore
AGENTS.md
AGENTS.md
LICENSE
LICENSE
README.md
README.md
package.json
package.json
pnpm-lock.yaml
pnpm-lock.yaml
pnpm-workspace.yaml
pnpm-workspace.yaml
View all files
Repository files navigation
Zenbu.js is a JavaScript framework for building hackable software.
Documentation<br>DeepWiki<br>Discord<br>Try the demo →
Get started in 5 seconds
npx create-zenbu-app
Why Zenbu.js
Coding agents can generate and customize software on demand for a specific use case. A hackable app gives them full access to do that.
Letting people modify your app means more directions get explored than you could reach on your own.
Extensible code tends to be more maintainable, because it’s already written to be changed.
How does it work
Users can modify Zenbu apps in 2 ways:
Modifying the raw source code
When a Zenbu app is built for production, there is no TypeScript compilation or bundling step. The same source code you wrote in development will be downloaded by the user and stored in ~/.zenbu/. When the app launches, it discovers the app code, dynamically compiles it, and runs the JavaScript using Electron's Node.js runtime.
All the source code in this directory is being watched for changes. When there is a change, the app will re-run affected code nearly instantly (also known as hot reloading). Hot reloading is implemented both in the main process and the renderer process.
The codebase stored inside ~/.zenbu/ is tracked by git. This makes it possible for a user to edit the source code without losing changes when the application code gets updated. The git repo is linked to a remote repository owned by the developer, so updates are represented as running git pull on the user's device.
Injecting plugins
Editing the raw source code of the application can be risky. If a user and the developer have conflicting edits, the user needs to spend time merging changes. This motivates plugins - a way to inject code into the application that can modify behavior without editing the raw source code.
Plugins run in the same process as the application code and get access to the same APIs. This means any feature written in the main app could be written as a plugin.
When you write an app in Zenbu your code is extensible by default , so plugins can extend it without you designing a plugin API up front. For more complex parts of your app that need a richer extension model, you can define your own on top.
Plugins hot reload just like application code, because application code is itself implemented as a plugin.
What this is not
Zenbu.js is not a one-size-fits-all model for building extensible applications. It provides a general-purpose way to load external code, with primitives for hot reloading, sharing state, and extending UI. For more complex behavior that isn't covered by Zenbu's architecture, you'll need your own conventions and systems for how that part gets extended, defined inside your Zenbu app.
Compatibility
Runtime<br>Status
Electron<br>🧪 Alpha
Node.js<br>🚧 WIP
Tauri<br>🚧 WIP
Browser-native<br>🚧 WIP
Roadmap
Non sandboxed out-of-process plugins
Improved sandboxing controls for plugins
Performance work
Migrate custom node HMR to Vite's environments API
HMR for node_modules, advice, and content scripts
Windows and Linux support
Automatic CLI per app
Git-based auto updater
WebRTC adapter for zenrpc and kyju (the database)
Add optimized production mode that pre-compiles and bundles the typescript to javascript (would opt project out of allowing its source code edited at runtime by user)
Support for running outside of electron (local node.js process + website, within tauri,...