Question 1

How do I fix Magnitude error "grammar binding failed: Too many items (limit 50000; mask)" when using tools or outputSchema?

Accepted Answer

Upgrade Magnitude to v0.2.6 or later; this grammar-binding regression was fixed in that release. On Magnitude 0.2.5, the workaround is to remove the nested `outputSchema` from the tool definition or reduce/simplify the registered tool schemas. The failure occurs before generation and is not caused by insufficient RAM.

Question 2

Why is Magnitude inference 5–6x slower than llama.cpp for the same GGUF model on Apple M4, and how do I fix it?

Accepted Answer

This was a macOS performance regression in Magnitude's old llama.cpp-based inference engine/background service. Update the Magnitude CLI to **0.0.13 or later**; the issue is also resolved by the new inference engine in **v0.2.0+**.

1. Stop the loaded model/service:
   ```bash
   magnitude models stop
   ```
2. Update Magnitude:
   ```bash
   npm install -g @magnitudedev/cli@latest
   ```
3. Confirm the version:
   ```bash
   magnitude --version
   ```
4. Reload the model and verify Metal acceleration:
   ```bash
   magnitude models load gemma-4-e2b-it-qat:gguf:q4
   magnitude hardware
   ```

After updating, generation throughput should be comparable to `llama-server -ngl 99` on the same GGUF and hardware.

Question 3

How do I block `javascript:` and `data:` URLs in markdown links rendered with react-markdown?

Accepted Answer

Upgrade to `react-markdown@9`; its `defaultUrlTransform` already rewrites dangerous protocols such as `javascript:`, `data:`, and `file:` to an empty string. For an explicit allowlist of only `http:`, `https:`, and `mailto:`, pass a custom `urlTransform` and render rejected links as plain text: ```tsx import ReactMarkdown, { defaultUrlTransform } from 'react-markdown'; const ALLOWED_PROTOCOLS = new Set(['http:', 'https:', 'mailto:']); function safeUrlTransform(url: string) { const transformed = defaultUrlTransform(url); if (!transformed) return ''; const base = globalThis.location?.origin ?? 'http://localhost'; const { protocol } = new URL(transformed, base); return ALLOWED_PROTOCOLS.has(protocol) ? transformed : ''; } href ? {children} : <>{children}, }} > {markdown} ``` Add regression tests for `javascript:alert(1)`, `data:text/html,...`, and `file:` URLs. Do not rely only on Electron CSP because the web UI may run in a normal browser without it.

Question 4

How do I fix “release request failed” when running `magnitude setup`?

Accepted Answer

Upgrade Node.js to version 18 or newer because the Magnitude launcher requires the built-in `fetch` API. Check your current version with `node -v`, then install Node.js 18+ and run `magnitude setup` again. If the error persists, verify your network can access the release assets and disable or reconfigure any VPN/proxy that may block the download.

Question 5

How do I fix the Ctrl+R Recent Conversations selection moving off-screen and not loading more pages when using arrow keys in the CLI?

Accepted Answer

The bug occurs because the overlay checks scroll position during React rendering and pagination depends on scroll events; keyboard navigation changes the selected index without scrolling the container.

The fix (PR #86) is to:
1. Replace render-time scroll polling with the existing `useInfiniteScroll` lifecycle.
2. Assign stable IDs to conversation rows.
3. Call OpenTUI's `scrollChildIntoView` after every Up/Down navigation so the selected `>` row stays visible.
4. Clamp the selection when refreshed results become shorter.
5. Continue loading pages until the viewport has a usable scroll range, then request one page when the bottom threshold is reached.

Update to a CLI build containing PR #86. On older builds, use the mouse or trackpad to scroll inside the Ctrl+R overlay and trigger pagination; arrow keys alone will not load the next page. Note that the affected built-in agent was later removed, so current builds may not include this overlay.

Magnitude

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects