Skip to content

Guides

Configure your project

Record goals, products, integrations and public preferences.

Resume the existing interview

Read the interview state before asking again. Answers cover conduction, credentials by variable name, databases, memory, products, topology, architecture, skills and auditing. An already configured project can resume without repeating the interview.

ork onboarding
ork onboarding show --json

Record public information

Use ork onboarding set to record a stage with attribution. Review the output before publishing the interview to memory. DSNs, tokens and passwords do not belong in public answers; configuration refers to protected variables. Without --por, the recorded author is owner, which does not prove that a person answered. Secret values live in the process environment or in the host vault (in Hermes, ~/.hermes/.env); onboarding stores only the variable name and never reads the value.

ork onboarding set produtos --conteudo '{"produtos":["meu-produto"]}' --por operador

Conversation preferences

The maestro stage also offers to activate the experience pack with detected values, configure it or turn it off. An answer with the owner object stores language, timezone, depth and activation in the manifest, preserving other sections and answers. Reading preferences creates no answer, authorship or approval. ork doctor warns when the interview time zone differs from the manifest; with owner.timezone in the same maestro answer, the warning compares that value, and the legacy fuso field applies only without it.

ork experiencia show --json
ork onboarding set maestro --conteudo '{"owner":{"language":"en-US","timezone":"UTC","depth":"curta","experience":true}}' --por equipe

Dispatch runtimes

Onboarding does not choose a runtime: the project default is the manifest’s runtime.adapter, and each block’s setup switches it per block, with ork setup <mode> --bloco N --runtime R --model M. Each runtime authenticates with its own account: ork accounts add <id> --runtime R --dir D runs the runtime CLI’s own login, and the core never reads the credential.

claude-bg and Codex serve as the project default, a block runtime and a fallback, each through its vendor’s subscription. Grok Build comes in as a block runtime and a fallback, always with the model the owner chose, and never as the project default: ork accounts add <id> --runtime grok --dir D logs in with the Grok subscription (with --device-auth, through a device code), and the child process runs without XAI_API_KEY.

In version 0.6.10, Grok Build has no live validation yet. Still open in RM-067: the format of an exhausted quota (until the live trial, automatic account switching never acts on it), checking the login without reading the credential, and the live trial itself. The core’s MCP server runs outside the sandbox of the Grok Build session, which, at the workspace floor, writes through the core.