OpenCode is an open-source AI coding agent platform that provides a multi-interface development environment including a desktop app (Electron), terminal UI (TUI), CLI, web console, and headless server. It integrates with numerous LLM providers (Anthropic, OpenAI, Google, Groq, etc.) and offers session management, a plugin system, file editing, shell commands, and real-time collaboration features. The architecture is a monorepo with packages for core logic, UI components, server, SDK, and integrations. Key entry points include the CLI (`opencode`), TUI, desktop app, and web console. Data flows involve session event sourcing, LLM request routing, and database persistence (SQLite locally, PlanetScale for cloud). External dependencies include Effect-TS, SolidJS, Electron, Bun, and various LLM provider APIs. The codebase demonstrates high craftsmanship with extensive use of Effect-TS for functional effect management, a well-defined plugin system, and a rich set of UI components built with SolidJS and Kobalte. It includes comprehensive testing (unit, e2e, performance benchmarks) and a robust CI/CD pipeline. However, the monorepo is large and complex, with some duplication between UI versions (v1/v2) and experimental features that may introduce drift. Overall, it is a well-engineered, actively maintained project suitable for reuse of its core patterns and components.

SST is a full-stack deployment framework and CLI tool for building and deploying serverless applications on AWS and Cloudflare. It uses Pulumi for infrastructure as code, provides a rich set of high-level components (Functions, Buckets, Queues, Databases, Auth, etc.), and supports multiple runtimes (Node.js, Python, Go, Rust) and frontend frameworks (Next.js, Remix, Astro, SvelteKit, SolidStart, etc.). The CLI offers live development mode with hot-reload, a terminal multiplexer, and SSH tunneling for VPC resources. The codebase is a monorepo with a Go CLI, TypeScript platform components, and SDKs in JavaScript, Python, Rust, and Go. While it demonstrates solid engineering patterns like a typed event bus, component transform system, and resource linking, it suffers from some deprecated components, code duplication across framework-specific SSR site components, and a high maintenance surface due to the sheer number of providers and examples.