Ecosystem metrics
- New Repos
- 8
- down 99.6%
- Commits
- 856
- down 3.7%
- Releases
- 4
- down 66.7%
- Contributors
- 50
- up 4.2%
- Merges
- 34
- up 30.8%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
6789 commits in all time
May 29, 2026 07:54 – Aug 27, 2026 07:54 UTC
skills(marketing): title cards are HTML, not ffmpeg drawtext
drawtext cards look like conference slides. The website promo's cards were HTML rendered through headless chromium, which is why they looked better -- brass rule, spaced kicker, big statement with an amber payoff line, CSS scanlines. make-card.sh makes that repeatable and scales the type to the frame, so a card matches its tape size instead of being letterboxed. Also record two things that cost a session each: vhs needs ttyd installed, and a shell segment must set the terminal background to the brand ground or the cut to a TUI segment visibly jumps.
1399f70f
main
2/64 ++ 4 --
docs(readme): the requirements table was five clauses deep per row
Left column is the entity now (CLI, Explorer, keystore, templates, LocalNet); the platform keychain details and the docker group note move to prose under it, where they do not have to fit in a cell.
eb170f96
main
1/15 ++ 6 --
docs: the README promised an approval gate the MCP path does not have
'Every write pauses for your approval first' is true in the Explorer and false for `vibekit mcp`, which defaults to execute mode and signs through the keystore without prompting. The homepage repeated it. Scope both to the Explorer and name SIGNING=compose as the alternative. Also: the skills count was 8 in two places on the homepage and is 5, and the package subpath list omitted ./core.
bb668cdd
main
2/12 ++ 8 --
docs: the site still described ten packages and unverified platforms
Version pins in the installation reference pointed at alpha.0; the alpha notices said 'the packages'; macOS is now verified by hand and the Windows installer runs on a real runner every push.
e27b45f5
main
3/11 ++ 10 --
chore: release v1.0.0-alpha.2
Same tree as alpha.1 plus the formatter pass, so the tag points at a commit that is actually on main. No behavior change. Also ignore apps/web/next-env.d.ts: `next build` regenerates it in its own style every run, so formatting it makes the next build a diff.
3445952d
main
13/61 ++ 6 --
feat: one npm package, plus the alpha.1 release and a formatter
Flattened: everything after the alpha.0 tag, as one commit. The ten published packages were one artifact in ten wrappers — lockstep versions, ten manifests, ten release entries, and the workspace:* drift trap, buying no consumer anything. `preset` pulled in six of them regardless. Everything is now `packages/vibekit`, published as `@initlabs/vibekit` with subpath exports; each old package is a directory under `src/`, and tests mirror it under `test/`. The root export is the core contract, so `./preset` no longer drags four third-party plugins into a types-only import. @initlabs/vibekit-core -> @initlabs/vibekit @initlabs/vibekit-tools -> @initlabs/vibekit/tools[, /views] @initlabs/vibekit-agent -> @initlabs/vibekit/agent[, /config] @initlabs/vibekit-mcp -> @initlabs/vibekit/mcp[, /stdio, /http] @initlabs/vibekit-signer-keystore -> @initlabs/vibekit/signer-keystore @initlabs/vibekit-preset -> @initlabs/vibekit/preset @initlabs/vibekit-plugin-<name> -> @initlabs/vibekit/plugins/<name> The ten old names are unpublished. v1.0.0-alpha.1 is on npm and on GitHub with binaries for four platforms. Installers: the Windows PowerShell installer is restored and exercised on a real runner every push; three of its bugs are fixed with a comment each (Invoke-RestMethod collapsing a JSON array into one pipeline object, Join-Path throwing on a null APPDATA, and bare `irm` defaulting to http). The hero one-liner no longer resolves a stable channel that does not exist, and the alpha channel no longer depends on GitHub hoisting a mislabelled release. Tooling: `.prettierrc` pins the style the codebase was already written in (single quotes, no semicolons, 100 columns) and the tree is formatted to it. Without a config, `bun run format` silently rewrote every file to prettier's defaults. Markdown is ignored — prose here is hand-wrapped, and prettier pads tables to fixed widths and misaligns them on em-dashes. Also: `doctor` reports a missing node/npm instead of surfacing it as an opaque daemon timeout; the README gained a requirements table; PRODUCTION.md is cut to the one deferred item that is still live.
a617a6f5
main
273/4,279 ++ 3,166 --
refactor: collapse the ten npm packages into one @initlabs/vibekit
Ten packages carried ~5,900 lines as one artifact in ten wrappers: lockstep versions, ten manifests, ten release entries, and the workspace:* drift trap, buying no consumer anything. `preset` pulled in six of them anyway. Everything is now `packages/vibekit`, published as `@initlabs/vibekit` with subpath exports. Each old package is a directory under `src/`; tests mirror it under `test/`. The root export is the core contract, so `./preset` no longer drags four third-party plugins into a types-only import. - @initlabs/vibekit-core -> @initlabs/vibekit - @initlabs/vibekit-tools -> @initlabs/vibekit/tools[, /views] - @initlabs/vibekit-agent -> @initlabs/vibekit/agent[, /config] - @initlabs/vibekit-mcp -> @initlabs/vibekit/mcp[, /stdio, /http] - @initlabs/vibekit-signer-keystore -> @initlabs/vibekit/signer-keystore - @initlabs/vibekit-preset -> @initlabs/vibekit/preset - @initlabs/vibekit-plugin-<name> -> @initlabs/vibekit/plugins/<name> verify-packed packs one tarball and drops the overrides block that pinned the packages' own @initlabs peers. The changesets `fixed` group is gone. Done now because the old names are hours old with zero dependents; after anyone installs them this becomes a breaking change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
a4aa0035
main
209/604 ++ 1,802 --
docs: handover for collapsing the npm packages into one
b70fd3c4
main
1/171 ++ 0 --
fix(install.ps1): release tag resolved to every tag joined together
Invoke-RestMethod emits a JSON array as ONE pipeline object, so `Get-Releases | Where-Object` handed the whole array to $_. `-match` over an array returns the matching elements rather than a boolean, so the array was truthy and every release 'passed' the filter -- producing a download URL with all 14 tags in it. Assign first, then iterate. Also: Join-Path threw on a null $env:APPDATA when checking for pre-1.0 state. CI now runs install.ps1 for real under Windows PowerShell 5.1 instead of only parsing it. The parse check passed on every one of these bugs.
2ba6c2a7
main
2/40 ++ 12 --
fix(website): hero PowerShell command omitted https://
Bare 'irm getvibekit.ai/...' defaults to http, and Windows PowerShell will not follow the 308 upgrade to https -- it reports the redirect as an error. curl -L follows it silently, which is why this only broke on Windows.
202f1ce2
main
2/4 ++ 2 --
docs(readme): Linux needs the docker group for LocalNet
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
bf43743a
main
1/1 ++ 1 --
docs: requirements sections, and record the Node-free keystore finding
Signing needs node and building needs node 24+, which the install story did not say plainly. README and the installation page now split what works with nothing installed from what needs a toolchain. PRODUCTION.md gets the prototype result: a compiled binary read the real OS keychain with no node on PATH, blocked only by two upstream packaging details. Also drops the install.ps1 and installation-docs entries, both now done.
b7c907a1
main
3/80 ++ 20 --
fix(keystore): a missing node failed as an opaque daemon timeout
The managed keystore CLI is a '#!/usr/bin/env node' program, so node must be on PATH to run the daemon -- not just npm to install it. Without node the spawn succeeded, the daemon died instantly, and the only trace of the real cause was 'env: node: No such file or directory' in the log file. doctor never checked node or npm at all, so a machine that could not sign still reported 'No blocking problems found'.
98a694ba
main
2/25 ++ 1 --
Merge 16ccbf512b56c4408fddd8f6d57b3c0d3586ac4d into 1192421795497e128a08550cbfd8f83b393dc614
4b39ebb0
pull/6713/merge
2/15 ++ 17 --
fix(website): the hero handed Windows visitors a bash command
PowerShell cannot run 'curl ... | VIBEKIT_CHANNEL=alpha sh' at all, and the command was long enough to overflow the hero box and slide under the copy button. - /alpha and /alpha.ps1 serve the canonical installers with the channel pre-set, so both one-liners are short - the hero swaps to the .ps1 form on Windows - the copy button reads the rendered command, so it cannot drift from it
67dae57b
main
6/83 ++ 5 --
fix(install): the hero one-liner resolved stable, which does not exist yet
Also print the full alpha command in the prerelease error instead of just naming the variable. Revert the hero to the bare command when 1.0.0 ships.
cff1e901
main
4/10 ++ 4 --
feat(website): copy button on the hero install command
791358e1
main
2/17 ++ 2 --
feat(install): restore the Windows PowerShell installer
The 1.0 rewrite dropped install.ps1, so Windows had no install path and install.sh pointed at a URL that 404'd. - install.ps1, ported to 1.0: both binaries, v* tags only (the heritage cli-v* releases are excluded), same env vars as install.sh - served at /install.ps1 from the repo file, same ?raw pattern as /install - explore: resolve .exe sidecars, so the installed vibekit-tui.exe is found - docs: real install instructions for both platforms; the page still said the public install channel did not exist - CI: parse install.ps1 on a Windows runner, since nobody develops on Windows
5055c7eb
main
8/353 ++ 20 --
fix(install): PATH hint hardcoded ~/.local/bin, ignoring VIBEKIT_INSTALL_DIR
1b6238eb
main
1/4 ++ 4 --
fix(install): Windows hint pointed at a nonexistent install.ps1
f8c235d2
tags/pre-1.0-history
1/1 ++ 1 --
Merge 54e2f69a9e30face7ed088f549fae42a11e1c3ea into 4bb8bde04aa890c23cdd067bd167c1f0375a632d
22699c08
pull/185/merge
3/78 ++ 7 --
feat(website): real mainnet assets in the hero table
6e2690f9
main
1/7 ++ 7 --
feat(website): the hero Explorer tabs actually switch pages
f246f537
main
2/141 ++ 5 --