Getting started
myetern is an infinite canvas where the diagram is the data: nodes have a type and fields, values flow along edges, the graph executes, and a document assembles from blocks. It works in the browser or as an app, together and in real time.
Account and sign-in
Register on the site, confirm your e-mail, sign in. The Open canvas button in the header of every page leads to the app. The browser app recognises you by the site session; the desktop app signs in with a code: it shows the code, you confirm it in the browser.
Teams and workspaces
Every workspace belongs to a team. Registration creates a personal team; team teams are created in the cabinet. The tree team → project → workspace opens from the button with the workspace name in the toolbar. New workspaces are created there too: empty or from a gallery template.
The first sign-in in the cloud opens nothing by itself: the app asks you to pick a workspace or create your own.
Three panels
- Canvas in the middle. Pan by dragging empty space, zoom with Ctrl and the wheel, select with a marquee.
- Palette on the right: search over node types, favourites, My components and Shared. A click creates a node in the centre of the screen, dragging places it at a point.
- Inspector on the left: scene tree, layers, types; below them the properties of the selected node. Long text is easier in the editor behind the ⤢ button.
Keyboard shortcuts
| Keys | Action |
|---|---|
| Ctrl+K | command palette: search over every action |
| Ctrl+Z, Ctrl+Y | undo, redo |
| Ctrl+D | duplicate the selection |
| Ctrl+C, Ctrl+V | copy and paste nodes with edges, across workspaces too |
| Del | delete the selection |
| Tab, Enter | subtopic and sibling for mind-map layouts |
| Arrows | move the selection by a grid step; Shift ×10 |
| Alt+arrows | jump to the neighbouring node in that direction |
| F2 | edit the node's main field |
| Ctrl+A | select every node on the level |
| Ctrl+], Ctrl+[ | raise or lower by z |
| Home | show everything |
| Esc | clear the selection and mode |
Working together and offline
Edits by different people do not overwrite each other: the document lives as a CRDT, text is edited character by character. Other people's cursors and selections are visible on the canvas. Without a network, edits accumulate and travel on the next connection with their original timestamps, so they never override anyone. The status line at the bottom always says what is going on: online, read only, session expired, workspace unavailable.
What next
Nodes and types, edges, layers and settings, data and files, the agent, languages, teams and permissions. Then the full cycle: code on the canvas with the editor and language servers, a project with jobs and a build chain, tasks and trackers, the database schema with migrations and the grid, Claude and MCP, and setting the workplace up for a task.