Everything Upfyn can do.

Getting Started

Upfyn runs as a native desktop app that turns your own computer into the execution engine. The web app at app.upfyn.com is a remote window into a paired desktop, not a separate cloud worker.

1. Install the desktop app

• Download Upfyn for Windows 10 or 11 from the Desktop page.
• One installer includes the assistant, local engine, browser tools, and scheduled work.

2. Sign in & pick a project

• Sign in with email or Google.
• Point Upfyn at a local project folder — each project keeps its own sessions, settings and working context.

3. Choose how you pay for models

Start on UpfynAI credits out of the box, or connect your own API keys (BYOK), local models, or your Claude or Codex subscription. See Models & Providers below.

Why Upfyn

Upfyn gives the tools already on your computer one assistant and one control layer. Start in Analyst for a simpler workspace, or use Developer when the job needs the full project, terminal, browser, Git, and specialist delegation.

• Local-first. The desktop coordinates files and machine tools on your hardware instead of moving the project into a rented cloud VM.
• Goal mode. Set a standing goal and let the orchestration layer plan, delegate, verify and surface anything that needs you.
• Choose the model route. Use UpfynAI credits, BYOK, compatible local models, or a supported Claude or Codex subscription.
• Extensible. MCP servers, Claude-Code skills and plugins, and custom agents drop right in.
• Open-core. The core is open source; the product is commercial.

Installation

Download the Windows installer from the Desktop page. The app auto-updates with cryptographically signed releases.

• Windows 10/11 — 64-bit
• Internet connection — for cloud models and updates (local models run offline)
• Chrome / Edge / Brave — optional, for browser automation

Prefer the browser?

Open app.upfyn.com to reach a paired desktop remotely. The desktop remains the engine and must be connected for local files and tools to run.

The AI Assistant

Upfyn is not a coding agent. It is the coordination layer that turns your machine into an assistant. Speak or type the outcome; Analyst coordinates analysis and everyday work, while Developer coordinates development across the full project, terminal, browser and Git.

• Plans a change, then edits files and runs commands to carry it out.
• Built-in tools: read / write / edit files, search, shell, web search and fetch, and more.
• Capability tools in the composer: Create Image, Search Web, Write Code, Deep Research, Think Longer.
• Fork, retry, revert, or edit any message to branch or redo work.

Modes

Choose the workspace that matches the job:

• Analyst — research, documents, connected apps, and scheduled work in a simpler workspace. It can read the active project and keeps its writes inside the project output folder.
• Developer — the full project, terminal, browser, Git, review tools, goals, and specialist delegation.

Both modes share the composer, voice, models, skills, and permission system.

Goal Mode

Goal mode works toward a standing goal: the orchestration layer plans the approach, delegates specialist work and keeps progress visible until the goal is complete or needs your input.

• Vishwakarma builds the change.
• The work is checked and verified to actually work.
• The result is reviewed pass or fail, and it keeps refining until the goal is met.

You can also open parallel side-chats — child sessions for subtasks — that appear under the main session.

Models & Providers

Use whatever models you like. Upfyn supports four ways to access them:

• UpfynAI gateway — credit-based access with no keys to manage.
• Bring your own key (BYOK) — Anthropic, OpenAI, Google, and many more.
• Local AI — Ollama or LM Studio (any OpenAI-compatible localhost), for fully private inference.
• Your subscription — drive sessions with your own logged-in Claude or Codex CLI; those turns report zero cost.

Pick a model per session, toggle which models show in the picker, and set reasoning effort per model.

Permissions

You decide what the assistant can do. Every tool — read, edit, write, shell, and more — is gated by the active permission rules.

• Ask — prompt before risky actions; allow once, always allow, or reject.
• Auto — only stop for risky actions.
• Bypass — unrestricted (off by default; enable in settings).
• Custom — rules from your config.

Auto-accept can be scoped to a session or a directory, and reads of sensitive files (like .env) always ask.

AI Browser

A browser the assistant can coordinate while you watch. It navigates, clicks, types, scrolls, extracts data and captures screenshots; a plan-first path can show the steps for approval before action.

• Live in-app browser panel with a side-by-side chat.
• It reads the page like a person, so it understands what's on screen.
• Optional Chrome extension to drive your real browser — connected locally, no headless sandbox.
• Also available as a built-in MCP browser server.

Workflows & Integrations

Connect an app from chat and its authorized tools become available to that conversation. Recurring work lives in Analyst mode and is coordinated by Upfyn's hosted Temporal service.

• Create and manage schedules without moving execution into a cloud worker.
• The desktop must be connected when a scheduled job needs local files, apps, or tools.
• Available connectors are shown in the desktop app; the catalog grows without changing the workflow.
• Set per-app tool access to always / ask / off.
• Workflow artifacts (HTML, markdown, text) save into your project.

MCP Servers

Upfyn connects to MCP servers to add tools, prompts, and resources. Connect local (stdio) or remote (HTTP / SSE, with OAuth) servers; their tools join the composer and their prompts become slash commands.

• Built-in servers: browser automation, workflows, and app integrations.
• Add your own local or remote servers from settings.
• Each server shows live status — connected, disabled, failed, or needs-auth.

Agents, Skills & Plugins

Upfyn is built to extend, and it's compatible with the Claude-Code ecosystem.

• Custom agents — reusable specialist prompts with their own permissions and model choices. Built-in responsibilities remain stages behind the one assistant.
• Skills — reusable markdown guides (SKILL.md) that appear in the slash menu as commands.
• Commands — built-in and custom slash commands, including MCP prompts.
• Plugins — install Claude-Code plugins; enabling mirrors their skills, agents, and commands in for the engine to discover.

Terminal, Files & Git

A docked, resizable right panel brings a full workspace into the app:

• Terminal — a real shell on your machine.
• Files — a file tree with tabs.
• Review — Git review and live diffs of changes made through the assistant.
• Browser and Side chat — automation and parallel subagents, side by side.

Voice

Talk to Upfyn instead of typing. Click the mic to dictate into the composer, and the speaker on a reply to have it read aloud.

• Speech-to-text dictation, with a browser fallback.
• Text-to-speech read-aloud, offline by default.

Memory

Plain-Markdown context the assistant reads every turn. Project memory files (AGENTS.md, CLAUDE.md, UPFYN.md) and global instructions keep it grounded in how you work — edit them from settings.

Usage & Cost

A live context-and-cost ring in the session header tracks tokens and spend as you go.

• Total tokens versus the model's limit, and the percentage used.
• Input, output, reasoning, and cache breakdown, plus USD cost.
• Compaction summarizes older context to free room.

Web Access

Prefer the browser? app.upfyn.com runs Upfyn on the web — the same AI chat, terminal, files, and git — with no install. Sign in with the same account.

Settings

A searchable, tabbed settings surface grouped into Personal, Integrations, Coding, and Account.

• General appearance, theme, fonts, and sounds.
• Providers, models, MCP servers, and integrations.
• Agents and memory files.
• Keybindings and a command palette.

Security

Upfyn is local-first by design.

• File and terminal operations stay on your machine; the selected model receives the context required for its reasoning turn.
• Bring-your-own-key credentials are stored locally and sent only to the provider you choose.
• Fine-grained permissions gate every tool; Analyst limits its own writes to the project output folder.
• Updates are cryptographically signed and verified before they install.

API Keys & BYOK

Bring your own provider keys and use any supported model — you're never locked to one provider.

• Add keys under Settings → Providers (Anthropic, OpenAI, Google, and more).
• Keys are stored locally and transmitted only to the provider you choose.
• Or skip keys entirely with UpfynAI credits, local models, or your Claude / Codex subscription.

Plans

Use your own keys, local models, or your Claude / Codex subscription, or buy UpfynAI credits for gateway access with no keys to manage. See the pricing page for current plans.

FAQ

Does my code get sent to the cloud?

File operations happen on the desktop and your project is not copied into a cloud worker. A selected cloud model still receives the context needed for its turn; choose a compatible local model when that context must remain on the machine.

Can I use it offline?

Yes — the desktop app runs without internet using local models (Ollama or LM Studio). Cloud models and updates need a connection.

Which models are supported?

Claude, GPT, Gemini, and many more via BYOK or the UpfynAI gateway, plus local models through Ollama and LM Studio — or your own Claude or Codex subscription.

Can I use it on my phone?

Yes, by pairing the web experience with your signed-in desktop. The phone is a remote window; the connected desktop remains the engine for local files and tools.

Is it open source?

Upfyn is open-core: the core is open source, while the desktop product itself is commercial software. See our Open-source licenses page for the full notices.