Prepare isolated dependencies
From the repository root, install Node.js 22.19 or newer, npm, Python 3.10 or newer, and PostgreSQL. Create two disposable databases using your normal PostgreSQL administration process: one for development and one for tests. The role must be able to create schemas and tables. Do not point either URL at production or an existing personal Hexagon installation.Start and inspect the control plane
http://127.0.0.1:18787/console/. Inspect authenticated health through the launcher; a listening socket alone is not readiness. doctor reports optional cloudflared and OpenSSH availability too: cloudflared is needed for temporary development credential ingress, and OpenSSH is needed for Instabox. See installation for ingress configuration before cloud execution.
A development Console can be inspected without creating cloud connections. Do not enable cloud runners as part of this first change. If the port is occupied or startup remains pending, inspect the selected private service log and process identity before attempting another start. Keep development and personal installations in separate databases/data directories and use distinct ports if running simultaneously.
For foreground debugging, stop the managed instance first, then use npm run db:migrate followed by npm run dev with the same selected development environment. dev is not a file-watching command. Do not run two workers against your development dataset accidentally.
Make one small, reviewable change
A suitable first task is clarifying the E2B template prerequisites in both translations of the E2B guide. Read the linked connector and dated evidence; change only wording justified by those sources. Preserve the distinction between the built-in OpenCode memory requirement and Session-owned OCI template preparation. Follow the concrete workflow in documentation contributions. For that documentation-only edit, run the structural checker and compare both translations:TEST_DATABASE_URL. verify runs TypeScript checking and Vitest; installed-package verification builds and consumes a Python wheel and npm tarball in temporary directories. Neither command is real cloud acceptance. Review the exact scope and additional startup/backup requirements in testing. A release audit is a check, not publication authorization.