Browse
Macrokit Studio logo

Macrokit Studio

Updated

In short

Macrokit Studio is a free AI developer tool SDK that routes GitHub tasks to pre-authored macros via a tiny local model — no API key or cloud needed.

What is Macrokit Studio?

Macrokit Studio is an AI developer tools SDK that routes repetitive GitHub maintenance tasks to pre-authored macros using a tiny local model running entirely in the browser for developers and open-source maintainers. Rather than sending every request to a cloud API, Macrokit Studio separates two distinct phases: at design time, a strong model authors a macro — a recorded, reusable workflow — and at runtime, a small local model (as compact as Qwen2.5 0.5B) classifies incoming tasks and routes them to the matching macro, executing the work with no API key, no server, and no cloud cost. The demo ships with three pre-built macros targeting public GitHub repositories: triage_newest_pull() for inspecting and labeling the newest open pull request, summarize_open_issues() for listing open issues with labels and comment counts, and repo_health() for reporting stars, open-issue count, and default branch status. Model inference runs via WebGPU directly in the browser, and users can choose between Qwen2.5 0.5B (fastest), Qwen2.5 1.5B, or Llama 3.2 3B for better routing accuracy. A live local coverage meter shows what percentage of session requests are being served by macros rather than a cloud model. All macros operate in dry-run write mode against public repositories only — no accounts or private data are accessed. The open @macrokit/* SDK underpins the studio and is designed so that as novel tasks are handled by the strong model, the resulting macros accumulate in a library, progressively increasing the share of work served locally at zero marginal cost. Best for: open-source maintainers and developers who want to automate repetitive repo tasks locally without recurring API costs.

What is Macrokit Studio used for?

GitHub repo maintenance automation, pull request triage, open issue summarization, repository health reporting, local AI macro routing, developer workflow automation

How much does Macrokit Studio cost?

Plan

Price not published

Pricing not published — the studio demo is free; visit the website or the @macrokit/* SDK repository for current plans

View pricing

Pros and cons

Pros

  • Runs entirely in the browser via WebGPU — no API key, no server, and no cloud model required at inference time
  • Ships with three ready-made macros (triage_newest_pull, summarize_open_issues, repo_health) that work immediately against any public GitHub repo
  • Supports three local model sizes (Qwen2.5 0.5B, Qwen2.5 1.5B, Llama 3.2 3B) so users can trade speed for routing accuracy
  • Live local coverage meter shows in real time what fraction of requests are served by macros versus a cloud model
  • Open SDK (@macrokit/*) allows design-time macro authoring so repeat tasks cost $0 once a macro is recorded

Cons

  • Currently limited to public GitHub repositories only — private repos and other platforms are not supported
  • Macro library is small (3 pre-built macros) and expanding it requires design-time authoring with a strong external model
  • WebGPU support is not universal across browsers and hardware, which may block some users from running local inference
  • Pricing for the full SDK or any hosted tiers is not published on the homepage

Questions about Macrokit Studio

What is Macrokit Studio?

Macrokit Studio is a free browser-based demo for the open @macrokit/* SDK. It lets developers run pre-authored AI macros against public GitHub repositories using a tiny local model (WebGPU) — with no API key, no server, and no cloud calls required at runtime.

Is Macrokit Studio free?

The studio demo is free and open. It runs locally in your browser with no account or payment required. Pricing for broader SDK tiers or hosted plans is not published on the homepage.

How does Macrokit Studio work?

At design time, a strong model authors a macro — a recorded workflow for a specific task. At runtime, a small local model (as small as Qwen2.5 0.5B) classifies your request and routes it to the matching macro, which executes against the live GitHub API. This means repeat tasks are served locally at $0 with no cloud round-trip.

What tasks can Macrokit Studio automate?

The current macro library covers three GitHub maintenance tasks: triaging the newest open pull request (with file inspection and label proposals), summarizing open issues by label and comment count, and reporting repository health metrics (stars, open-issue count, default branch). New macros can be added at design time using the SDK.

How does Macrokit Studio compare to GitHub Copilot or OpenAI Codex?

Unlike GitHub Copilot or Codex, which stream every request to a cloud model, Macrokit Studio routes repetitive tasks to pre-authored local macros that run in the browser via WebGPU. This means zero API cost and no latency for repeat tasks, but Macrokit currently targets repo-maintenance workflows rather than inline code completion.

What are the best alternatives to Macrokit Studio?

Reviews

Sign in to rate and review Macrokit Studio.

Sign in to review

No reviews yet. Be the first to review Macrokit Studio!

Visit Macrokit Studio