13.1 Claude Code Full Experience
Claude Code is Trellis’s primary platform, with the most complete automation capabilities. Three core Hooks form the automation loop:
| Hook | Trigger Timing | Capability |
|---|
session-start.py | SessionStart | Auto-injects context (identity, history, tasks) |
inject-subagent-context.py | PreToolUse (Task) | Auto-injects precise Spec context for Agents |
ralph-loop.py | SubagentStop (check) | Auto-verifies code quality (Ralph Loop) |
- Hook auto-injection — start working immediately upon opening terminal, no manual
/start needed
- Multi-Agent Pipeline —
/parallel orchestrates multiple worktree Agents in parallel
- Ralph Loop — automatic quality gate, Check Agent auto-retries on failure
- Agent system — 6 specialized Agents (dispatch, plan, implement, check, debug, research)
13.2 Cursor Integration
trellis init automatically generates Trellis command files under .cursor/commands/:
| Claude Code Command | Cursor Equivalent |
|---|
/trellis:start | /trellis-start |
/trellis:before-dev | /trellis-before-dev |
/trellis:brainstorm | /trellis-brainstorm |
/trellis:check | /trellis-check |
/trellis:check-cross-layer | /trellis-check-cross-layer |
/trellis:finish-work | /trellis-finish-work |
/trellis:break-loop | /trellis-break-loop |
/trellis:create-command | /trellis-create-command |
/trellis:integrate-skill | /trellis-integrate-skill |
/trellis:onboard | /trellis-onboard |
/trellis:record-session | /trellis-record-session |
/trellis:update-spec | /trellis-update-spec |
- Files located at
.cursor/commands/trellis-{name}.md
- Cursor has 12 commands (no
/parallel, as Cursor doesn’t support Multi-Agent Pipeline)
- No Hook support — spec injection requires manual command invocation
- No Agent system — all work happens in the main conversation
- No Ralph Loop — check commands must be run manually
Recommended workflow for Cursor users:
# 1. Start session (required, replaces Hook auto-injection)
/trellis-start
# 2. Load relevant specs (recommended, replaces PreToolUse Hook)
/trellis-before-dev
# 3. Describe task, AI develops...
# 4. Manually check code quality (replaces Ralph Loop)
/trellis-check
/trellis-check-cross-layer # Cross-layer check
# 5. Finish checklist
/trellis-finish-work
13.3 Codex Integration
trellis init --codex -u your-name
AGENTS.md (root directory) — Codex entry file, provides base project context (similar to CLAUDE.md).agents/skills/ — Shared Agent Skills directory (agentskills.io open standard, used by Codex, Kimi CLI, Amp, Cline, and others).codex/config.toml — Project-scoped Codex configuration.codex/agents/ — Custom Codex agents (implement.toml, research.toml, check.toml).codex/skills/ — Codex-specific skills (e.g. parallel for multi-agent pipelines).codex/hooks/session-start.py + .codex/hooks.json — SessionStart hook that injects Trellis workflow, guidelines, and task context into Codex sessions
As of Codex CLI v0.116.0 (2026-03-24), hooks are an experimental feature that requires manual opt-in. Add this to ~/.codex/config.toml:[features]
multi_agent = true
codex_hooks = true
13.4 Kilo Code Integration
Kilo Code is an open-source (Apache 2.0) AI coding Agent platform, available as a VS Code extension, JetBrains plugin, and CLI, with 750K+ users.
trellis init --kilo -u your-name
.kilocode/ directory:
What Trellis generates for Kilo:
trellis init --kilo generates workflow files under .kilocode/workflows/. These are Kilo’s equivalent of slash commands — invoked in chat as /start.md, /check.md, etc.
| Trellis / Claude Code | Kilo Code (generated by Trellis) | Description |
|---|
.claude/commands/*.md | .kilocode/workflows/*.md | Workflow commands invoked as /start.md, etc. |
project/
├── .kilocode/
│ └── workflows/ # Commands (equivalent to slash commands)
│ ├── start.md # /start.md — session init
│ ├── brainstorm.md # /brainstorm.md
│ ├── before-dev.md # /before-dev.md
│ ├── check.md # /check.md
│ ├── check-cross-layer.md # /check-cross-layer.md
│ ├── finish-work.md # /finish-work.md
│ ├── break-loop.md # /break-loop.md
│ ├── create-command.md # /create-command.md
│ ├── integrate-skill.md # /integrate-skill.md
│ ├── onboard.md # /onboard.md
│ ├── parallel.md # /parallel.md
│ ├── record-session.md # /record-session.md
│ └── update-spec.md # /update-spec.md
Kilo also supports rules/, rules-code/, rules-architect/, skills/, launchConfig.json, and mcp.json — but these are not generated by Trellis. You can create them manually if needed. See Kilo Code documentation for details. # 1. Run the start workflow for full context
/start.md
# 2. Switch to Orchestrator mode for complex tasks
# Kilo auto-decomposes tasks and assigns to Code/Architect modes
# 3. Describe task, AI develops...
# 4. Run check workflow
/check.md
# 5. Finish
/finish-work.md
Kilo’s Orchestrator Mode shares a similar philosophy with Trellis’s Multi-Agent Pipeline, but the implementation differs:
Trellis uses git worktree physical isolation + Hook orchestration, while Kilo uses built-in mode switching + independent conversation context.
The two are complementary — Trellis’s Spec management and Task system provide structured project context for Kilo.
13.5 Kiro Integration
Kiro is an AI IDE by Amazon, built on Code OSS (VS Code open-source core), focused on Spec-Driven Development. It supports IDE, CLI, and Autonomous Agent modes.
trellis init --kiro -u your-name
trellis init --kiro generates skill files under .kiro/skills/. Each skill is a SKILL.md file with YAML frontmatter, following the Agent Skills open standard.
| Trellis / Claude Code | Kiro (generated by Trellis) | Description |
|---|
.claude/commands/*.md | .kiro/skills/*/SKILL.md | 12 skills with YAML frontmatter |
project/
├── .kiro/
│ └── skills/ # Agent Skills (YAML frontmatter + instructions)
│ ├── start/SKILL.md
│ ├── brainstorm/SKILL.md
│ ├── before-dev/SKILL.md
│ ├── check/SKILL.md
│ ├── check-cross-layer/SKILL.md
│ ├── finish-work/SKILL.md
│ ├── break-loop/SKILL.md
│ ├── create-command/SKILL.md
│ ├── integrate-skill/SKILL.md
│ ├── onboard/SKILL.md
│ ├── record-session/SKILL.md
│ └── update-spec/SKILL.md
Kiro also supports steering/, hooks/, specs/, prompts/, agents/, and settings/ directories — but these are not generated by Trellis. You can create them manually if needed. See Kiro documentation for details. # 1. Use the start skill to initialize session context
# 2. Describe task, AI develops...
# 3. Use the check skill to verify code quality
# 4. Use the finish-work skill for pre-commit checklist
# 5. Commit code when done
13.5b CodeBuddy Integration
CodeBuddy is Tencent Cloud’s AI coding assistant, supporting IDE and CLI forms with MCP extensibility.
trellis init --codebuddy -u your-name
trellis init --codebuddy generates command files under .codebuddy/commands/trellis/. These are invoked in chat as /trellis:start, /trellis:check, etc.
| Trellis / Claude Code | CodeBuddy (generated by Trellis) | Description |
|---|
.claude/commands/*.md | .codebuddy/commands/trellis/*.md | 12 slash commands in Trellis namespace |
project/
├── .codebuddy/
│ └── commands/ # Slash commands
│ └── trellis/ # Trellis namespace
│ ├── start.md # /trellis:start
│ ├── brainstorm.md # /trellis:brainstorm
│ ├── before-dev.md # /trellis:before-dev
│ ├── check.md # /trellis:check
│ ├── check-cross-layer.md # /trellis:check-cross-layer
│ ├── finish-work.md # /trellis:finish-work
│ ├── break-loop.md # /trellis:break-loop
│ ├── create-command.md # /trellis:create-command
│ ├── integrate-skill.md # /trellis:integrate-skill
│ ├── onboard.md # /trellis:onboard
│ ├── record-session.md # /trellis:record-session
│ └── update-spec.md # /trellis:update-spec
CodeBuddy also supports .rules/, agents/, settings.json, and hooks — but these are not generated by Trellis. You can create them manually if needed. See CodeBuddy documentation for details.
- Files located at
.codebuddy/commands/trellis/{name}.md
- CodeBuddy has 12 commands (no
/parallel, as CodeBuddy doesn’t support Multi-Agent Pipeline)
- No Hook support at Trellis level — spec injection requires manual command invocation
- No Agent system integration — all work happens in the main conversation
Recommended workflow for CodeBuddy users:
# 1. Start session (required)
/trellis:start
# 2. Load relevant specs
/trellis:before-dev
# 3. Describe task, AI develops...
# 4. Check code quality
/trellis:check
/trellis:check-cross-layer
# 5. Finish checklist
/trellis:finish-work
13.6 Operating System Compatibility
| OS | Support Status | Notes |
|---|
| macOS | ✅ Full support | Primary development platform, all features verified |
| Linux | ✅ Full support | All features verified |
| Windows | ✅ Full support | All scripts migrated to Python, natively supports Windows |
| Consideration | Details |
|---|
| Python scripts | Scripts under .trellis/scripts/ are Python, requiring Python 3.8+, cross-platform compatible |
| Python Hooks | Hook scripts under .claude/hooks/ require Python 3.8+, cross-platform compatible |
| Path separators | Trellis internally uses /, Python handles path conversion automatically |
| Git worktree | Multi-Agent Pipeline relies on git worktree, supported on all platforms |
13.7 Multi-Developer Collaboration
Non-conflicting parts (per-developer isolation):
workspace/{name}/ — each developer has their own directory.developer — gitignored, per-developer- Parallel task worktrees — physically isolated
Potentially conflicting parts (require coordination):
spec/ — multiple people may modify the same spec simultaneouslytasks/ — multiple people may operate on the same task
Best practices:
- Spec changes go through PR review
- Task assignments are explicit (
--assignee parameter)
- Important spec changes are discussed in team meetings
13.8 Complete worktree.yaml Configuration
# Worktree Configuration for Multi-Agent Pipeline
#───────────────────────────────────────────────────
# Paths
#───────────────────────────────────────────────────
# Worktree storage directory (relative to project root)
worktree_dir: ../trellis-worktrees
#───────────────────────────────────────────────────
# Files to Copy
#───────────────────────────────────────────────────
# Files that need independent copies in each worktree
# These files contain sensitive info or need independent config
copy:
- .env # Environment variables
- .env.local # Local environment variables
- .trellis/.developer # Developer identity
#───────────────────────────────────────────────────
# Post-Create Hooks
#───────────────────────────────────────────────────
# Commands to run after creating a worktree
# Executed sequentially in the worktree directory; aborts on failure
post_create:
- pnpm install --frozen-lockfile
# - npm install
# - yarn install --frozen-lockfile
#───────────────────────────────────────────────────
# Check Agent Verification (Ralph Loop)
#───────────────────────────────────────────────────
# Commands to verify code quality
# When configured, Ralph Loop runs these — all must pass
# Without configuration, falls back to completion markers mode
verify:
- pnpm lint
- pnpm typecheck
# - pnpm test
13.9 trellis update and Version Management
# Check current version
cat .trellis/.version
# Update to latest version
trellis update
# Preview updates (dry run)
trellis update --dry-run
# Force overwrite all files
trellis update -f
# Skip all changed files
trellis update -s
.trellis/.template-hashes.json stores the SHA-256 hash of each template file. During trellis update:
- Compute local file hashes
- Compare with recorded template hashes
- If they match — file not modified by user — safe to update
- If they differ — file was modified by user — prompt for conflict resolution
- User chooses: overwrite / skip / merge
