Arvore Repo Hub

Changelog

Releases

Every version of Repo Hub CLI, from the first commit to the latest feature.

Latest: v0.16.0
v0.16.0 Latest

Chat consolidation

New hub consolidate command extracts knowledge from chat sessions across Kiro, Claude Code, and OpenCode into team memories — using the editor's own CLI as the LLM engine.

Feature
hub consolidate — Reads chat history from Kiro, Claude Code, and OpenCode, compacts sessions into a batch, and spawns the editor CLI (kiro-cli, claude, or opencode) to extract decisions, conventions, gotchas, and domain knowledge into ./memories/. Zero extra dependencies — uses the model you already pay for.
Feature
Cross-editor session collection — Auto-detects chat storage for Kiro (Application Support JSON), Claude Code (~/.claude/projects JSONL), and OpenCode (~/.local/share/opencode session/message/part). Normalizes all formats into a unified structure.
Feature
Incremental processing — Tracks indexed sessions in .hub/consolidation-state.json. Running hub consolidate twice won't reprocess the same sessions. Use --reset to start fresh.
Fix
Session ordering — Collectors now sort globally by date before applying the limit, ensuring the most recent sessions are always processed first regardless of which workspace directory they're in.
v0.15.0

Enhanced orchestrator prompts

All editor generators now produce richer orchestrator prompts with core behavior, working style, code change, security, git discipline, and skills listing sections. AGENTS.md is now generated universally across all editors.

Feature
AGENTS.md for all editors — All editor generators (Cursor, Claude Code, OpenCode, Kiro) now write AGENTS.md at the workspace root. Kiro no longer generates a duplicate .kiro/steering/orchestrator.md.
Feature
Core behavior sections — Six new shared sections added to all orchestrator prompts: Core Behavior, Working Style, Search/Reading/Investigation, Code Changes, Security/Safety, and Git/Operational Discipline. Based on analysis of Cursor and Claude Code system prompts.
Feature
Skills listing in orchestrator — The orchestrator prompt now includes a Skills section that lists all available skills with descriptions, associated repositories, and guidance on when to consult them.
v0.14.0

Kanban MCP

Persistent kanban board MCP for AI agent task management with multi-session coordination, semantic search via LanceDB, and parallel chat visibility.

Feature
Kanban MCP Server — New @arvoretech/kanban-mcp with 12 tools for board and card CRUD, semantic search, subtasks, and session management.
Feature
Multi-session — Each chat identifies with a session_id. claim_card and release_card enable coordination between parallel chats. get_board shows active sessions with duration.
Feature
Semantic search — search_cards uses LanceDB with multilingual embeddings to find cards by semantic context.
Feature
Helper mcp.kanban() — New RHM CLI helper to configure the kanban MCP in hub.config.ts.
v0.13.4

OpenCode orchestrator as primary agent

The OpenCode orchestrator is now generated as a primary agent with default_agent in opencode.json, matching the arvore-hub pattern. Also fixes env var format in MCP config and generates a .ignore file for repo discovery.

Feature
Orchestrator as primary agent — The orchestrator is now written to .opencode/agents/orchestrator.md with mode: primary and default_agent: orchestrator in opencode.json, instead of being a rule file in .opencode/rules/.
Feature
Generate .ignore file — hub generate now creates a .ignore file listing all repo names with ! prefix, enabling tools like ripgrep and OpenCode to discover repo directories.
Fix
OpenCode env var format — MCP environment variables in opencode.json now use the correct {env:VAR} format instead of ${env:VAR} or ${VAR}, matching the OpenCode spec.
Fix
Clean up stale orchestrator rule — Regenerating now removes the legacy .opencode/rules/orchestrator.md file to prevent conflicts with the new primary agent.
v0.13.3

Fix YAML frontmatter in design source skills

Design source skills with colons in the description field now generate valid YAML frontmatter. Previously, the unquoted colon in 'Design source: name' caused SKILL.md parsing errors.

Fix
Quote description in skill frontmatter — The buildSkillContent function in design-sources.ts now wraps the description value in double quotes, preventing YAML parsing failures when the value contains colons.
v0.13.2

Gitignore .agent-teams

The .agent-teams directory is now automatically added to .gitignore when agent-teams-lead MCP is configured. Previously, manually adding it would get wiped on hub generate.

Fix
Persist .agent-teams in .gitignore — The buildGitignoreLines function now conditionally includes .agent-teams/ when the agent-teams-lead MCP is detected, so hub generate no longer removes it from the managed block.
v0.13.1

Agent Chat

Cross-developer agent communication via Slack threads. Your agent can now talk to agents from other developers on the team — opening threads, replying, and checking for new messages proactively.

Feature
Agent Chat MCP — New agent-teams-chat MCP that connects agents to a shared Slack channel. Agents post with their owner's identity and communicate through threads. Five tools: open_thread, reply_to_thread, read_thread, list_threads, find_thread.
Feature
Proactive Message Checking — The orchestrator actively monitors for responses after sending messages. It polls threads periodically and checks recent threads for relevant context when starting new tasks.
Feature
Configurable Message Format — Messages use handlebars-style templates (e.g. 🤖 *{{identity}}'s Agent* — {{message}}). Customizable via the MESSAGE_TEMPLATE environment variable.
Feature
Automatic Orchestrator Instructions — When agent-teams-chat MCP is detected in your config, hub generate injects an Agent Chat section into the orchestrator prompt with tool docs, proactive polling behavior, and best practices.
v0.13.0

Agent Teams

Inspired by Anthropic's Claude Code agent teams, now available across every editor. Spawn multiple AI teammates that work in parallel, share a task list, and message each other directly.

Feature
Agent Teams — Your orchestrator can now act as a team lead, spawning multiple AI teammates that work in parallel on different tasks and communicate with each other through a shared mailbox. Built as an editor-agnostic MCP layer that works with Kiro, Cursor, Claude Code, and OpenCode.
Feature
Automatic Orchestrator Instructions — When agent-teams-lead MCP is detected in your config, hub generate injects a full Agent Teams section into the orchestrator prompt with tool docs, workflow guidance, and best practices.
Feature
Task Coordination & File Locking — Tasks support dependencies and exclusive file paths to prevent conflicts. Atomic mkdir-based file locking ensures safe parallel work when multiple teammates try to claim the same task.
Feature
Inter-agent Messaging — Teammates communicate through a shared mailbox with typed messages (info, question, answer, blocker, decision). Direct messages, broadcasts, and lead messages are all supported.
v0.12.1

Security fix for runtime-lens MCP

Fix runtimeLens helper to use the correct scoped package @arvoretech/runtime-lens-mcp instead of the unscoped runtime-lens.

Fix
Scoped package name for runtime-lens — The mcp.runtimeLens() helper was resolving to the unscoped runtime-lens npm package, which could install an unrelated or malicious package. Updated to use @arvoretech/runtime-lens-mcp.
v0.12.0

hub clone

New hub clone command for cloning all repositories without running full setup. Clone first, setup later.

Feature
hub clone — Clone all repositories defined in your config without starting services, installing tools, or running dependency installation. Auto-detects SSH vs HTTPS, with --ssh and --https flags to force a specific method.
v0.11.0

React Native Support

First-class React Native/Expo support with repo.reactNative() helper, auto-detection in hub scan, TUI integration, and JSON Schema validation.

Feature
repo.reactNative() Helper — New type-safe helper for React Native projects with sensible defaults (pnpm install, pnpm start, pnpm build, pnpm test, pnpm lint).
Feature
React Native Auto-Detection — hub scan now detects app.json, app.config.js, and app.config.ts as react-native projects, preventing misidentification as plain React.
Feature
TUI Integration — hub init infers react-native for repos with mobile or app in the name. REPO_HELPER_MAP maps react-native to repo.reactNative for correct hub.config.ts generation.
Feature
JSON Schema Update — react-native added to the tech enum in hub.schema.json, enabling autocompletion and validation in hub.yaml.
v0.10.0

Interactive TUI & TypeScript Config

hub init is now a full interactive TUI built with ink — a multi-step wizard with registry integration, tech stack detection, and MCP selection. Plus TypeScript config support with type-safe helpers for repos, MCPs, and services.

Feature
Interactive TUI — hub init launches a polished terminal UI with 11 steps: welcome, name, editor, repos, agents, skills, MCPs, config format, summary, creating, and done. Agents and skills are fetched from the hub directory registry, with smart pre-selection based on your tech stack.
Feature
TypeScript Config — Define your hub config in hub.config.ts with full type safety. The defineConfig wrapper provides autocompletion, and composable helpers (repo.nestjs, mcp.postgresql, service.postgres, etc.) set sensible defaults for each framework and tool.
Feature
Config Helpers — Type-safe helpers for 7 repo frameworks, 17 MCP servers (all arvore-mcp-servers packages plus Playwright and Context7), and 8 Docker service types. Each helper pre-fills the correct package names, default commands, ports, and images.
Feature
Directory Registry Integration — The TUI fetches agents and skills from hub.arvore.com.br/directory.json at runtime. Skills matching your repo tech stack are automatically recommended. Falls back to built-in defaults when offline.
Feature
Three.js Hero Animation — The website landing page now uses a Three.js particle animation for the hero section, replacing the previous inline canvas implementation.
v0.9.0

Remote Sources & Design System

Skills and steering files can now live outside your repo — in Notion, at a URL, or on a local path. Plus a new design section in hub.yaml that teaches the AI your visual language: component libraries, icon systems, and design tokens.

Feature
Remote Sources — Define skills and steering files that live in Notion pages, raw URLs, or local filesystem paths. During hub generate, content is fetched, converted to markdown (with full Notion block support including tables, toggles, code blocks, and images), and installed into your editor config automatically.
Feature
Design System Config — New design section in hub.yaml lets you declare UI libraries (with MCP, URL, or local docs), icon libraries, design skills, and free-form instructions. The orchestrator prompt now includes a structured Design System section so the AI always knows which components and tokens to use.
Feature
MCP Description & Instructions — MCP configs now support description and instructions fields. Descriptions appear in the orchestrator's MCP listing, and instructions are injected as per-server guidance so the AI knows how to use each tool correctly.
Feature
Auto-generate .env.example — hub generate scans all MCP env vars across your config and produces a .env.example file, so new team members know exactly which secrets to configure without reading through hub.yaml.
Fix
Path Traversal Guard — Remote sources with local paths now validate that the resolved path doesn't escape the workspace directory, preventing accidental reads of files outside the project.
Fix
Fetch Timeout — URL-based remote sources now use a 30-second AbortSignal timeout, so hub generate doesn't hang indefinitely on unreachable endpoints.
Fix
Schema Validation — Fixed anyOf validation in the JSON schema for remote sources and design libraries, ensuring proper editor autocompletion and validation in hub.yaml.

Install the latest version:

$ npx @arvoretech/hub@latest