The init experience got a complete overhaul. Instead of a few CLI prompts, hub init now launches a full interactive TUI built with ink — a multi-step wizard that walks you through every decision. And if YAML isn’t your thing, you can now define your hub config in TypeScript with composable, type-safe helpers.

Interactive TUI for hub init

The old hub init was a handful of inquirer prompts. The new one is a proper terminal UI with 11 steps, live feedback, and a polished flow:

Welcome → Name → Editor → Repos → Agents → Skills → MCPs → Format → Summary → Creating → Done

Each step renders a dedicated screen that clears the terminal for a clean experience. Here’s what changed:

Repos step lets you add multiple repositories with URL and tech stack detection. Type a GitHub URL, pick the tech (nestjs, nextjs, react, elixir, go, python), and it builds the list interactively.

Agents and Skills are fetched from the hub directory at runtime. You see the full registry of available agents and skills with descriptions, and skills that match your repo tech stack are pre-selected with a ★ marker. If the registry is unreachable, sensible defaults kick in.

MCPs step shows all 14 available MCP servers from arvore-mcp-servers — databases, monitoring, feature flags, email, browser testing, and more.

Format step is new — you choose between YAML and TypeScript for your hub config (more on that below).

Summary shows everything you picked before creating. You can go back to change the format or confirm to proceed.

Creating runs each setup task with a spinner and checkmarks as they complete — creating directories, writing config, installing agents and skills from the registry.

The TUI is built with ink and React, using custom components for each step type: WelcomeStep, NameStep, SelectStep, MultiSelectStep, ReposStep, SummaryStep, CreatingStep, and DoneStep.

TypeScript Config (hub.config.ts)

You can now define your hub configuration in TypeScript instead of YAML. The CLI auto-detects hub.config.ts in your workspace root and loads it via dynamic import (with tsx as fallback for environments without native TS support).

defineConfig

Wrap your config in defineConfig for type checking and autocompletion:

import { defineConfig, repo, mcp, service } from "@arvoretech/hub/config";

export default defineConfig({
  name: "my-company",

  repos: [
    repo.nestjs("api", "git@github.com:company/api.git"),
    repo.nextjs("frontend", "git@github.com:company/frontend.git"),
    repo.elixir("backend", "git@github.com:company/backend.git"),
  ],

  mcps: [
    mcp.postgresql("main-db"),
    mcp.datadog(),
    mcp.playwright(),
    mcp.memory(),
  ],

  services: [
    service.postgres("db"),
    service.redis("cache"),
  ],

  workflow: {
    pipeline: [
      { step: "refinement", agent: "refinement" },
      { step: "coding", agents: ["coding-backend", "coding-frontend"] },
      { step: "review", agent: "code-reviewer" },
      { step: "deliver", actions: ["create-pr", "notify-slack"] },
    ],
  },
});

Repo helpers

Each helper sets the tech stack and default commands for that framework:

All helpers accept an optional overrides object to customize commands, skills, env_file, and other fields.

MCP helpers

Pre-configured helpers for every MCP server in arvore-mcp-servers, plus community servers:

Service helpers

Docker Compose services with sensible defaults:

Config resolution

The CLI checks for config files in this order:

1. hub.config.ts (TypeScript)
2. hub.yaml (YAML)

Both formats support the same schema. The cache system includes both files in its inputs hash, so changes to either trigger regeneration.

Scan command

When using TypeScript config, hub scan detects new repos in the workspace and shows the suggested repo.*() helper call instead of auto-modifying the file:

Found new repo: payments (nestjs)
  → Add to hub.config.ts: repo.nestjs("payments", "git@github.com:company/payments.git")

Website: Three.js Hero

The landing page hero section now uses a Three.js particle animation (HeroScene.ts) instead of the previous inline canvas implementation. Smoother, more performant, and easier to maintain.

Upgrade

npx @arvoretech/hub@0.10.0 generate

Or if you have it installed globally:

hub generate

Existing hub.yaml configs work without changes. TypeScript config is opt-in — create a hub.config.ts and the CLI picks it up automatically.