Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

layout default
title OpenCode AI Legacy Tutorial
nav_order 138
has_children true
format_version v2

OpenCode AI Legacy Tutorial: Archived Terminal Agent Workflows and Migration to Crush

Learn from opencode-ai/opencode architecture and workflows, and migrate safely to actively maintained successors.

GitHub Repo License Successor

Why This Track Matters

This repository is archived, but still useful as a reference for terminal-agent UX patterns, multi-provider model routing, and migration planning to maintained tools.

This track focuses on:

  • understanding archived OpenCode behavior and capabilities
  • operating legacy workflows safely when needed
  • planning migration to Crush and related maintained stacks
  • preserving useful patterns without carrying unbounded legacy risk

Current Snapshot (auto-updated)

Mental Model

flowchart LR
    A[Terminal task] --> B[OpenCode TUI]
    B --> C[Provider and model routing]
    C --> D[Tools and shell actions]
    D --> E[Session storage and compaction]
    E --> F[Migration to maintained successor]
Loading

Chapter Guide

Chapter Key Question Outcome
01 - Getting Started and Project Status How should I approach an archived coding-agent project? Safe baseline
02 - Legacy Architecture and Feature Model What did OpenCode optimize for in terminal workflows? Architecture understanding
03 - Installation and Configuration Baseline How do I reproduce legacy setups reliably? Reproducible setup
04 - Model Providers and Runtime Operations How do provider and environment settings affect behavior? Better runtime control
05 - Interactive and Non-Interactive Workflows How do I automate tasks in legacy mode? Workflow clarity
06 - Session, Tooling, and Integration Practices How do I manage sessions/tools/MCP configs safely? Operational stability
07 - Migration to Crush and Modern Alternatives How do I move off archived infrastructure? Migration plan
08 - Legacy Governance and Controlled Sunset How do teams retire legacy usage responsibly? Sunset runbook

What You Will Learn

  • how to evaluate and use archived coding-agent tooling safely
  • how to reproduce and document legacy OpenCode behavior
  • how to plan and execute migration to maintained successors
  • how to manage governance and risk during legacy sunset periods

Source References

Related Tutorials


Start with Chapter 1: Getting Started and Project Status.

Navigation & Backlinks

Full Chapter Map

  1. Chapter 1: Getting Started and Project Status
  2. Chapter 2: Legacy Architecture and Feature Model
  3. Chapter 3: Installation and Configuration Baseline
  4. Chapter 4: Model Providers and Runtime Operations
  5. Chapter 5: Interactive and Non-Interactive Workflows
  6. Chapter 6: Session, Tooling, and Integration Practices
  7. Chapter 7: Migration to Crush and Modern Alternatives
  8. Chapter 8: Legacy Governance and Controlled Sunset

Generated by AI Codebase Knowledge Builder