How htoooth/qwen-code works
Project type and purpose
• Qwen Code is a monorepo-style developer tool—a Node.js/TypeScript CLI application with an accompanying core library and VS Code extension.
• Purpose: Provide interactive AI-driven code understanding, editing, and workflow automation via Qwen3-Coder models and an enhanced parser.
File structure
Top-level folders and files:
• scripts/, Makefile, Dockerfile, .github/, .aoneci/, .gcp/ → build & CI/CD pipelines
• docs/ → architecture, CLI tutorials, troubleshooting
• integration-tests/ → end-to-end tests of CLI tools
• packages/
– cli/ → user-facing command-line interface (Ink/React in terminal, commands, config, sandbox utils)
– core/ → AI integration (model client), tool scheduler/registry, built-in tools (fs, shell, web-fetch, memory), services (file discovery, git, telemetry)
– vscode-ide-companion/ → VS Code extension host + IDE server bridging to core
• root config (tsconfig.json, esbuild.config.js, eslint.config.js)
Extract architecture insights from README & docs
• Layered CLI ↔ Core boundary: CLI package handles UI, input parsing, presentation; Core package handles business logic, tool orchestration, AI requests, telemetry.
• Tools are pluggable modules registered centrally and invoked by the Core tool scheduler.
• Sandbox isolation profiles for macOS to securely invoke host tools.
• CI/CD uses GitHub Actions, aoneci, and GCP build/release to produce Docker images and NPM packages.