GuideTools3 min read
The editor: bring it all together
Your work, collections, contract controls, wallets, and agents share one workspace. Keep the whole project in view.
Select an underlined word to see what it means.
In this guide
A name travels through the project.
Change the name, then open Collection or Artist page. They use the same draft.
You should not have to rebuild the context every morning.
Public download coming soon
Your sketch has files. Your release has a collection and mint rules. Your profile has a story. Your agent needs to know which project it is changing. The editor is where those threads meet.
Try the workspace tour above. Move from the work to its collection, page draft, agent, and wallet review. It is an interactive illustration of the flow, with future page and plugin ideas marked.
Make a change. See where it belongs.
Edit and preview the work. Keep its metadata, references, and release decisions in the project. Link contracts by network and address, inspect their controls, and use the assistant with the context you choose.
The SDK supplies shared project tools. MCP gives agents a structured way to use them. The editor brings those capabilities into a place you can see and organize.
| Area | What it helps you do |
|---|---|
| Files and notes | Keep the editable project and saved decisions together. |
| Preview | See supported local media or try the HTML work in an isolated view. |
| PartsReusable components included in a work, with their own identities and permissions.For exampleSeveral artworks can share the same verified drawing library.Full glossary entry → | Browse runtime and protocol catalogs. |
| Contracts | Inspect known controls and prepare an unsigned change. |
| Assistant | Share selected context with the configured assistant provider. |
| Saved workspace | Keep local project records with checks against overwriting newer saves. |
Wallets are working. Review remains yours.
The desktop editor already has wallet connections and reviewed contract actions. It supports installed EVM wallets and Tezos wallet connections; signing stays in the selected wallet.
Importing an ABI can produce contract controls. Before a write, the review shows the account, network, destination, action, and value. A saved address or an agent suggestion does not grant permission.
Technical detail: local persistence and context sharing
The workspace uses revision-checked SQLite records and content-addressed object imports. API credentials use operating-system encryption outside project memory. Assistant integrations require explicit context selection; sending context to a provider is different from an entirely local preview. Imported ABIs describe methods but do not verify code identity or chain authority.
We built the connections. What will you bring?
A painting that opens with its history. A world that reads its characters’ equipment. A collection with your own rules. A tool another artist can build on.
Start with one work. Follow its files, decide how it can change, and give people a way to find it. The engine, the SDK, the agent tools, and the editor are there to help you take the next step.
Make the workspace yours.
The planned editor and SDK plugin system can bring specialized tools into this flow: an admin page for your collection, a custom inspector, or a workflow built for your medium.
Modules remain the pieces inside the artwork. Plugins extend the tools used to build and manage it. Your personal page and agent workflows belong in this wider vision, with profile and project tools providing the foundation today.