Skip to content

Tools

Tools

Learn the focused workbenches Varc provides for querying, inspecting, changing, and automating Redis and Valkey.

Varc groups focused work into tools in the Dock. Each tool has its own workflow, keyboard shortcuts, limits, and reference pages. This hub is the starting point for those guides.

Query tools

SQL Query

Use familiar SQL to find Redis or Valkey keys, inspect values, and update key names, scalar values, TTLs, or collections. The reference covers Varc’s supported dialect, type-aware functions, bounded execution, partial-commit behavior, and saved queries.

UPDATE redis
SET ttl_ms = 60000
WHERE key LIKE 'session:%'
RETURNING key, ttl_ms
LIMIT 100;

Start with your first SQL query, or go directly to the language reference.

Automation tools

Scripts

Run bounded TypeScript against the connected Redis or Valkey server, inspect console output and returned values, then save repeatable work as a manual script or command macro.

const expiring = await redis.scan(0, { match: "session:*", count: 100 });
return { database: redis.database, sampled: expiring.keys.length };

The guide covers editor tabs, device-local drafts, saved scripts, run output, permissions, environments, and macro slots.

Transformers

Create pure TypeScript decoders for binary values. Preview a draft with sample UTF-8 input, save it, then select it from the Saved group in supported value viewers.

import { toString } from "varc:bytes";

return { kind: "text", body: toString(value) };

The guide covers the transformer result contract, key-pattern metadata, viewer availability, safe rendering, raw-byte fallback, and the tighter transformer sandbox.

How tool documentation is organised

Every tool section begins with an everyday workflow. Deeper pages then document its language or commands, results, safety limits, and persistence model. Tool reference pages appear beneath that tool in the sidebar while you are inside its section.

The Scripts and Transformers workflow guides live here with the other desktop tools. Their shared language, APIs, modules, environments, permissions, and execution-class contracts remain in the deeper Scripting reference.