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

@arandevcode/opencode-thinking

v0.2.2

Published

Theme-aware visual thinking indicators for opencode — rainbow border (warning/error), IDLE state in success color, and construction sidebar

Readme

@arandevcode/opencode-thinking

🇪🇸 Also available in Spanish

Animated visual indicators when the model is processing — rainbow border around the input area and sidebar glow. No config needed.

Install

opencode plugin --global --force @arandevcode/opencode-thinking

Or install from GitHub source to follow latest development:

// ~/.config/opencode/opencode.json
{
  "plugin": [
    "https://github.com/arandevcode/opencode-plugins/tree/main/opencode-thinking"
  ]
}

Uninstall

Three steps, in order:

  1. Remove the plugin entry from your OpenCode config (~/.config/opencode/opencode.json):

    // delete the @arandevcode/opencode-thinking lines inside "plugin": []
    {
      "plugin": [
        "@arandevcode/opencode-thinking/tui",   // ← remove
        "@arandevcode/opencode-thinking/server" // ← remove
      ]
    }
  2. Delete the shared state file the plugin uses for TUI ↔ Server IPC:

    rm -f ~/.config/opencode/thinking-visual-state.json
    rm -f ~/.config/opencode/thinking-visual-debug.log
  3. (Optional) Remove any local source clone you may have used to follow development:

    rm -rf ./opencode-thinking

Restart OpenCode and the rainbow border + sidebar glow will be gone.

Commands

| Command | Effect | |---|---| | /thinking_visual | Toggle all effects | | /thinking_visual a | Border animation only | | /thinking_visual b | Sidebar glow only | | /thinking_visual all | Both | | /thinking_visual none | Disable |

More Information

How activation works

Automatic (default): the plugin listens for session status. When opencode starts processing (session.status === "busy"), rainbow effects appear. When done (session.idle), they disappear.

Manual: use /thinking_visual or toggle individual modes via Command Palette (Cmd+K → "Thinking Visual").

Project structure

├── .opencode/
│   ├── opencode.json            ← project config (activates plugin + slash cmds)
│   └── plugins/
│       ├── opencode-thinking-tui.ts      ← TUI plugin (visual effects)
│       └── opencode-thinking-server.ts   ← Server plugin (handles /thinking_visual)
├── src/                         ← npm distribution source
│   ├── index.ts
│   ├── tui.ts
│   ├── server.ts
│   └── types.ts
├── docs/
│   └── ARCHITECTURE.md
├── example.opencode.json
└── package.json

.opencode/plugins/ lets the plugin work without npm install, without build, without global install — opencode loads them automatically from the project.

Install in another project

// .opencode/opencode.json
{
  "plugin": [
    "@arandevcode/opencode-thinking/tui",
    "@arandevcode/opencode-thinking/server"
  ]
}

Development

npm install        # install deps (type-check only)
npm run build      # compile src/ → dist/
npm run dev        # continuous compilation

TUI Patterns & Theme

Colors are sourced live from api.theme.current, not hardcoded. The plugin also watches the theme signature (250ms polling) so theme changes mid-session are picked up by the next re-render.

| Phase | Border + badge color | Badge text | |---|---|---| | Working (model is busy) | alternates theme.warningtheme.error every 250ms | WORKING | | Idle (model is idle / session.idle) | theme.success | IDLE |

The same color drives the sidebar title border while the visual mode b is enabled.

This pattern follows the opentui-theme-colors convention: semantic theme keys (success / warning / error) instead of hardcoded palette values, and themeSignature() + setInterval polling for reactive theme changes.

License

MIT