Skip to content
NodeOS

NodeOS / Getting started

From first connection to your first development task.

A clear starting point for your team — and practical instructions for the developer connecting your agent.

  1. 01

    Get access to NodeOS

    Request a demonstration or beta access. The team arranges workspace access; this is not a self-service trial signup.

  2. 02

    Connect your development environment

    Use the hosted MCP connection and sign in with an authorized NodeOS account, or ask a workspace administrator for a scoped REST agent and API key.

  3. 03

    Install and configure the Starter Kit

    KIRO and Codex have full-kit adapters. Install from the folder opened in your IDE. Shared instructions and configuration still require review; this is not universal one-click onboarding.

  4. 04

    Connect the project and existing knowledge

    Organize tasks and make relevant decisions and published documentation available within authorized access. No automatic import or synchronization of every repository is promised.

  5. 05

    Start the first real task

    Retrieve context, verify the current code, start the appropriate work session and record checkpoints and evidence. Keep human verification separate from agent submission.

Agent Starter Kit · 2.3.0

For the developer

MCP approval selects a customer and agent identity within your rights. REST keys are provisioned by an authorized administrator. Keep credentials out of source files and chats.

Open the Starter Kit

macOS / Linux

curl -o nodeos-setup.mjs https://nodeos.dk/docs/agent-kit/setup.mjs
node nodeos-setup.mjs --tool kiro   # or --tool codex
node nodeos-setup.mjs --tool kiro --check

Windows (PowerShell)

Invoke-WebRequest -Uri https://nodeos.dk/docs/agent-kit/setup.mjs -OutFile nodeos-setup.mjs
node nodeos-setup.mjs --tool kiro   # or --tool codex
node nodeos-setup.mjs --tool kiro --check

MCP-only for other IDEs

node nodeos-setup.mjs --tool cursor   # or claude | vscode

No credentials are included in these commands. Authorization and the API key are set up manually by you.

Hosted MCP endpoint

https://nodeos.dk/mcp

Agent Starter Kit · 2.3.0

Connect your agent. Keep your development context.

The Agent Starter Kit gives connected development tools a repeatable way to work with NodeOS. Starter Kit 2.3.0 warns in preflight when your local kit is older than the published version, and checks for missing delivery evidence before a work session is completed.

  1. 01

    Get access

  2. 02

    Connect your development environment

  3. 03

    Install the Starter Kit

  4. 04

    Retrieve your first task with context

  5. 05

    Record work and preserve new knowledge

For the development owner

What is required?
Access to a NodeOS workspace during the private beta, arranged with the team. Your developer then connects their tools.
How does a workspace become available?
Access is reviewed and set up by the NodeOS team. Nothing is activated automatically.
What can the agent access?
Only what its connection allows: the tasks, decisions, documentation and evidence in the workspaces it is authorized for.
What history can it use?
Previous tasks, recorded decisions, documentation, development evidence and earlier work-session checkpoints.
How is progress recorded?
The agent records work sessions, checkpoints and evidence. People review the evidence — the agent cannot approve its own work.

For the developer

Prerequisites
Node.js 18 or newer, a NodeOS workspace and authorization from your workspace owner.
Supported tools
Full Starter Kit adapters: KIRO and Codex. Cursor, Claude Code and VS Code: documented MCP setup only, not full adapters.
Installation
Run the installer in the folder you open in your IDE (the parent of your repositories). Commands below.
Authentication
MCP uses OAuth in your tool's browser flow. REST uses a personal API key that you place in .env yourself — never in chat, code or commits.
MCP or REST
MCP endpoint: https://nodeos.dk/mcp. REST and OpenAPI documentation: /api/public/v1/docs.
Agent permissions
The agent acts with the rights of its connection. It cannot widen its own access or approve its own evidence.
First task
Ask the agent to fetch an assigned task with its parent tasks, decisions and documentation before it starts.
Troubleshooting
Run the --check command, confirm Node 18+, and see the Starter Kit README for known errors.
Demo · All names, numbers and information are fictional
Owner view Example company

Releases

Published · DEMO
Demo 0.2 · Welcome and overview

A new welcome page and a unified overview have been delivered in this fictional project.

Next planned release

Demo 0.3 · Notifications

Notifications and report export are planned for the next delivery.

Demo · All names, numbers and information are fictional

Build on what came before.

Give your people a shared overview. Give your agents a better starting point.

Request a demo