Phase 7 · desktop app and hardening

A local-first assistant that asks before it acts.

Friday is an AI coding and DevOps assistant that runs on your machine, as a Linux desktop app or a local web app. It reads, edits, tests and commits in projects you authorize, and it can diagnose servers, plan deploys and run approved SSH commands. Every change is shown to you first.

Bring a key you already have. Friday stores conversations and memories locally. API keys stay in your config file and are never written to the database.

NoTokenLimit Anthropic OpenAI OpenRouter Google Gemini 7API

Works on the project in front of you

Point Friday at a folder. It maps the code, edits with your approval, and checks the result against the project's own tests and build.

Read before it writes

File reads, search, a code map of classes and functions, and git status or diffs run without approval. Credential files stay unreadable, and search only reports that one matched, by name.

Edits you can undo

Changes are exact diffs, shown before they run. A re-check refuses a stale edit if the file moved. Undo and roll back a run refuse to overwrite work you made since.

Tests with a real report

Friday runs the project's suite and reports failures with file and line, flaky tests, and the slowest tests. A verification report is built from its records, not from the model's summary.

Git, review, and pull requests

Inspect freely. Commits, branches, pushes and pull requests need approval every time. Pushes never target the default branch and are never forced. Reviews land as a card, most severe first.

Task worktrees

Start a task on its own branch in a separate worktree, so your checkout stays untouched. Accept merges or squashes it back, keeps the branch, or discards it.

Rename and move symbols

Find references, rename a symbol across the project, or move a definition to another file, with the same approval and undo path as any other edit.

Approval is the product

Friday can propose a lot. It cannot apply an edit, run a command, open a shell on a server, or push a branch until you say so. Ask and Plan modes are enforced by the tool policy, not by a prompt.

AutoPicks an approach. May offer a mode switch. Never switches itself.
CodeImplements and verifies with tests, type-check or build.
PlanInvestigates and writes a plan. Changes nothing until you accept it.
DebugReproduces first, names the cause with evidence, then makes the smallest fix.
AskExplains only. Editing, commands, git writes and SSH are refused.

Task permissions

For a fix-and-retest loop, approve one bounded permission: named files, exact commands, a time limit and an action cap. Revoke it any time. Deletes, moves, git writes, SSH and high-risk commands are never covered.

Resume, don't restart

Progress is checkpointed after every action. If the app stops mid-task, Resume hands back what already changed and which commands ran. Pending approvals are cancelled so they cannot run late.

More than a chat box

The same approval model covers the rest of a working day: previews, documents, voice, memory, and the web.

Screenshots and preview

Paste or drop images, or let Friday look at PNG, JPEG, WebP and GIF files in the project. A live preview and recorded browser flows can exercise the UI you just changed.

Background processes

Dev servers and watchers start with approval, then can be read and stopped without another prompt. They show in a side panel with their local URL and a Stop button.

Documents

Ask for a PDF, Word, Excel or PowerPoint file and Friday writes it into the project. Export a conversation as Markdown or PDF, with secrets redacted.

Memory, per project

Durable facts: architecture, commands, decisions, procedures, and preferences you approve. Each answer shows which memories were used. Project memory stays isolated.

Voice, on this machine

Kokoro speaks replies and Whisper base takes dictation, both on the CPU. Models download only when you ask, audio is never stored, and saying "approve" never approves anything.

Web search and research

Look up current docs, release notes and errors, or run a longer research pass that cites its sources. Page text is treated as data, not instructions.

Connected apps, databases, and saved actions

MCP apps show up as extra tools under the same approval rules. Connected databases can be inspected and queried read-only. Saved actions are the procedures you keep for this project, such as a staging deploy, run as a named step instead of retyped instructions.

Token use you can see

Tools load in groups. Usage shows where input went, what optimization saved, and prompt-cache hits. Keys are never stored in SQLite.

DevOps, with the brakes on

Servers are opt-in. Friday stores a key path, never a password, and will not connect until you trust the host key.

This machine first

Environment checks, log search, config validation and health monitors run locally. Docker Compose status is read-only until you approve a control action.

CI, read-only

Ask why a GitHub Actions run failed. Friday uses your gh login for GET requests only, finds the first real error, and maps runner paths back to project files.

SSH with a plan

Read-only diagnostics, a deployment plan, then an approved remote command. Production needs the plan first, a five-minute approval, and the host name typed by you.

Dependencies

See what is outdated or vulnerable, read the release notes, and upgrade only through an approved change.

Load tests

Run k6 against this machine or hosts you have listed. It does not get a blank cheque to hit somewhere else.

Databases, read-only

Schema and approved SELECT-style queries on databases you connected. Writes are not a tool.

Install

The desktop app is a Linux AppImage or deb, with Node built in. From source it also runs as a local web app on Linux, macOS or WSL2.

  1. Desktop. 64-bit Linux, or WSL2 with WSLg. Grab the AppImage or deb from Releases. Nothing else to install.
  2. From source. Node.js 22.13 or newer (tested on 22.23) and npm. Clone the repo, install, and run npm run dev or npm start.
  3. Add one provider key in the env file Settings points at: NTL_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, OPENROUTER_API_KEY, GEMINI_API_KEY or SEVENAPI_API_KEY.
  4. Open a project and send a message. The server binds to 127.0.0.1. Data lives in ~/.config/Friday/data for the desktop app, or ./.data for the web app.

Useful scripts

npm run devAPI + Vite
npm testNo API key
npm run desktopApp from checkout
npm run dist:desktopAppImage and deb
npm run typecheckStrict TypeScript

Live integration tests are separate and use quota. See the README for the full configuration table.

Providers

Switching provider is choosing another model. Capabilities, context window and usage prices are kept per model id.

ProviderKeyModel id
NoTokenLimitNTL_API_KEYas listed, e.g. claude-sonnet-4.6
AnthropicANTHROPIC_API_KEYanthropic:claude-sonnet-4-6
OpenAIOPENAI_API_KEYopenai:gpt-5
OpenRouterOPENROUTER_API_KEYopenrouter:anthropic/claude-sonnet-4.6
Google GeminiGEMINI_API_KEYgemini:gemini-2.5-pro
7APISEVENAPI_API_KEY7api:…

Each provider address can point at a proxy or a compatible gateway. Timeout and retries apply to all of them. For multi-step work the project recommends claude-sonnet-4.6 or stronger, and probing a new model before relying on its tool use.

What stays on your machine

Local data

SQLite holds conversations, checkpoints, approvals, undo backups, memories and an audit log. The data folder is created 0700 and the database 0600.

Keys stay in the env file

API keys are read from config and are never stored in the database. SSH records keep the key path only. Friday does not read your git or gh credentials.

Localhost only

The server binds to 127.0.0.1. A lock file stops two servers from sharing one database. Quit, copy the data folder, and you have a backup.