npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@teamcode-ai/teamcode

v2.4.0

Published

Readme

TeamCode is an open source AI-powered coding agent that runs in your terminal. It helps you navigate, understand, and modify codebases through natural language conversations.


🚀 v2.0.0 — Go Core Engine

TeamCode v2.0.0 introduces a hybrid runtime architecture: a Go core engine that handles I/O-heavy operations alongside the existing TypeScript runtime, delivering significant performance improvements:

  • Filesystem operations — up to 10× faster reads, writes, and searches
  • Process spawning — cross-platform process execution with timeouts
  • File watching — real-time file change detection via SSE streaming
  • Session management — CRUD lifecycle with consolidated message history
  • Provider catalog — built-in registry of 25+ models across 8 providers
  • Configuration — hierarchical teamcode.json[c] loading with caching

The Go core runs as a sidecar process, automatically spawned when you run TeamCode. Feature flags control routing between the engines, with a circuit breaker that falls back to 100% TypeScript if the Go core encounters errors.


📦 Installation

Via npm (recommended)

npm install -g @teamcode-ai/teamcode
teamcode

From source

git clone https://github.com/ElioNeto/teamcode.git
cd teamcode
bun install
bun run --cwd packages/teamcode dev

🎮 Usage

# Start TeamCode in the current directory
teamcode

# Start with a specific project
teamcode /path/to/project

# Run a single prompt non-interactively
teamcode run "explain this codebase"

# List available providers and models
teamcode providers

# Enable debug logging (verbose output to stderr)
teamcode --debug
teamcode --debug run "describe this codebase"

Engine indicator

The TUI footer shows which engine is active:

  • ⚡Go — Go core running alongside TypeScript (shadow mode or canary)
  • TS — 100% TypeScript (Go core not available)

🤖 Agents

TeamCode includes two built-in agents you can switch between with the Tab key.

  • build — Default, full-access agent for development work
  • plan — Read-only agent for analysis and code exploration
    • Denies file edits by default
    • Asks permission before running bash commands
    • Ideal for exploring unfamiliar codebases or planning changes

Also included is a general subagent for complex searches and multistep tasks. This is used internally and can be invoked using @general in messages.


🏗️ Architecture

┌─────────────────────────────────────────────────────┐
│                  TeamCode CLI                        │
│  (Bun-compiled binary: teamcode)                    │
├─────────────────────────────────────────────────────┤
│  TypeScript Runtime        │  Go Core (sidecar)     │
│  ┌───────────────────┐     │  ┌──────────────────┐  │
│  │ TUI / UI          │     │  │ Filesystem       │  │
│  │ Session management│     │  │ Process spawning │  │
│  │ LLM integration   │     │  │ File watching    │  │
│  │ Plugin system     │     │  │ Session CRUD     │  │
│  │ Feature flags     │────┼──│→ Provider catalog │  │
│  │ Circuit breaker   │     │  │ Config loading   │  │
│  └───────────────────┘     │  └──────────────────┘  │
│                            │  localhost:43001        │
└─────────────────────────────────────────────────────┘

Debug Mode

Pass --debug to any command to enable verbose logging. This forces log level to DEBUG and prints logs to stderr, helping diagnose initialization bottlenecks, provider connection issues, and tool execution:

# Interactive TUI with debug logging
teamcode --debug

# Single prompt with debug logging
teamcode --debug run "explain this codebase"

# Debug persists into the TUI worker process

The debug flag is automatically forwarded to the background worker when using the TUI, so both the main thread and the server worker produce verbose output.

Shadow mode

Before routing traffic to the Go core, TeamCode runs both engines in parallel, compares results, and logs divergences. This shadow mode validates correctness without affecting your workflow:

FLAG_filesystem_shadow=true teamcode /path/to/project

Divergences are logged to stderr:

[shadow] divergence filesystem.read trace=<uuid> { ts: ..., go: ... }

🧪 Test Suite

500+ tests spanning both TypeScript and Go:

| Layer | Tests | Stack | |-------|-------|-------| | Go unit | 103 | go test | | TS core | 426 | bun test (core package) | | TS parity | 75 | bun test + Go core |

# Run Go tests
cd go-core && make test

# Run core package tests
cd packages/core && bun test

# Run parity tests (requires Go core binary)
cd packages/core && GO_CORE_BINARY=../../go-core/server bun test test/parity/

# Run a specific test file
cd packages/core && bun test test/models.test.ts

# Full typecheck across all packages
bun turbo typecheck

🤝 Contributing

If you're interested in contributing to TeamCode, please read our contributing docs before submitting a pull request.


Join our community Discord | X.com


Originally based on opencode (MIT)