Cross-tool execution
Run one instruction across local files, browser sessions, and selected desktop workflows.
Private by design
Give one instruction. Velyn plans visible steps across local files, browser sessions, and selected desktop workflows — then acts only with your approval.
macOS private alpha · local Ollama · approval-gated tools
Early access requests open in a BuildLayer form, prefilled for the Velyn private alpha.
What it does
Velyn links a single instruction to concrete actions across local files, browser sessions, and selected desktop workflows while keeping execution visible.
Give intent, inspect planned steps, and approve execution with full override.
Core capabilities
Run one instruction across local files, browser sessions, and selected desktop workflows.
Review explicit step-by-step actions before execution begins.
Keeps track of active tasks, open artifacts, and prior direction in the current workflow.
Helps with repeated operating tasks while preserving execution context.
Pause, revise, or stop execution at any point in the same thread.
Designed for codebases, multi-step flows, and tool-heavy daily work.
Privacy and control
Velyn is built so sensitive context stays on your Mac and key execution steps remain inspectable in Operations.
How it works
01
Describe what should be done in plain language.
02
Validate proposed actions across tools before execution starts.
03
Approve execution, guide progress, or interrupt when needed.
Use cases
Turn local notes and managed-browser research into reviewable draft summaries.
Apply file updates, run checks, and keep changes reviewable in one flow.
Handle repeated setup and operations tasks with less context switching.
Gather inputs from tabs, docs, and app output into a structured draft.
Alpha scope
Velyn is early software. These boundaries set expectations before you request access.
Packaged for Mac (Apple Silicon). Features, stability, and tool coverage evolve during early access.
Normal use runs AI on your Mac via Ollama. Setup guides you through installation; cloud LLM providers are not part of the alpha path.
Web work runs in a separate managed Chromium profile—not your daily Safari or Chrome session.
File tools respect allowlisted roots. Workflow actions use curated aliases, not control of every installed application.
FAQ
Plain-language answers aligned with the current macOS private alpha.
Access
Early access requests are handled through BuildLayer, the product studio building Velyn. The form opens with Velyn alpha details prefilled.
Request early access via BuildLayer ↗