Pixel Agents is a developer tool that visualizes AI coding agents (primarily Claude Code) as animated pixel-art characters in a virtual office environment. It ships as both a VS Code extension and a standalone CLI (`npx pixel-agents`), sharing a common runtime. The system monitors agent sessions in real-time via HTTP hooks (preferred) or JSONL file polling (fallback), normalizes events through a provider abstraction, and renders agent state (tool usage, context tokens, team structures, permissions) on a Canvas-based pixel-art office map. The architecture follows a hub-and-spoke pattern: a Fastify HTTP/WebSocket server aggregates agent activity, an AgentRuntime manages lifecycle and state, and a MessageTransport abstraction (PostMessage for VS Code, WebSocket for standalone) broadcasts updates to the React 19 + Canvas webview UI. The codebase is well-structured with clean interfaces (HookProvider, TeamProvider, StateAdapter), extensive test coverage (unit, integration, and Playwright e2e with a mock Claude CLI), and CI-enforced contract drift detection (AsyncAPI spec ↔ generated TypeScript, e2e inventory). While only the Claude provider ships, the provider registry is designed for multi-CLI support. The project demonstrates strong engineering practices with some complexity risks in dual-mode detection, consent flow edge cases, and cross-platform path handling.
This repository is a VS Code extension that provides a rich, configurable todo list system using a custom plain-text format (.todo, .todos, .task, etc.). It enables users to create, edit, toggle states (box, done, cancelled), archive tasks, track time with a timer, generate project statistics, and scan embedded todos within code files using external search tools (ag, rg). The extension contributes two custom activity bar views (Files and Embedded) and status bar items, all driven by a comprehensive configuration system for symbols, colors, tags, and formatting. The architecture follows a modular design with a clear separation of concerns: document parsing into typed items (Todo, Project, Comment, Tag, etc.), decorator classes for syntax highlighting, utility modules for file operations, time formatting, statistics computation, and embedded code scanning. The item classes form a clean class hierarchy with static `is()` methods for identification and state manipulation methods. The embedded providers abstract over multiple search backends (JavaScript, ag, rg) with a common interface, and the base TreeDataProvider uses an event emitter pattern to notify view updates. The extension is written in TypeScript, bundled with webpack, and relies on several utility libraries (lodash, moment, micromatch, etc.). While the codebase demonstrates solid engineering practices—reusable components, consistent naming, and a config-driven design—it has notable maintenance risks: heavy reliance on complex regexes for parsing, a moderately large dependency list, and no visible test infrastructure (no test files found in the file tree). The changelog mentions regressions and a fundraising prompt, indicating limited maintenance bandwidth. Overall, it is a functional and feature-rich extension that does its job well, but its internal complexity and lack of tests could hinder long-term reliability.
Gitlantis is a VS Code extension that turns the traditional file explorer into an interactive 3D ocean world. Users control a boat to navigate a seascape where directories appear as lighthouses and files as buoys, making code exploration more engaging. The extension communicates via webview with a React Three Fiber interface, offering features like branch switching, file opening, and settings customization. It also supports a standalone browser mode for demo purposes using sample data. Architecturally, the extension consists of a VS Code extension host that handles workspace and Git operations, and a rich webview application built with React 18, Three.js, React Three Fiber/Drei, and Zustand for state management. The 3D scene includes dynamic ocean tiling, boat physics (using React Three Cannon), collision-based node interaction, a compass, minimap, and ambient audio. The UI layer provides splash screens, loading states, settings modals with multiple tabs, and mobile joystick support. The codebase demonstrates modern frontend practices and creative use of 3D in a developer tool. However, it has several maintainability concerns: many @ts-expect-error comments for Three.js types, hardcoded demo data for browser mode, a complex dual-build setup, and no automated tests. Some components, like the settings modal and the dynamic backdrop, are well-abstracted and potentially reusable in other Three.js projects.