Friday

Install

npm install -g @archymedes/friday
friday

friday opens a session in the folder you run it in. friday "fix the failing test" opens one that starts on that request; friday --resume latest carries on where you left off. The engine is written in Go and runs inside the friday binary itself: nothing else to install or start.

The first run

The first time Friday opens, a walkthrough of six short steps sets it up: a name for the greeting (kept on your machine), a theme and a mode picked from tiles, four keys tried in place, the connection, and a first request to start from. enter goes on, backspace goes back, esc skips the rest. alt+w or /welcome opens it again.

To connect a model, pick a provider in the walkthrough or in Providers (alt+p) and paste its key. Free models need only an OpenRouter key; a Claude or ChatGPT plan signs in with its own tool.

How a request goes

You ask; Friday reads the project, plans, edits and runs what it needs, and says what it did. How much it may do alone is the mode, and shift+tab cycles it:

Before a turn that changed code may end, it has to show the change works: tests first and seen failing, then the code, then the project's own check. You see where it is in a row under the conversation.

Suggestions while you work

A turn that changed files ends with up to three next steps, each with why now: a check that failed, a change nothing has tested, a diff worth reading. Each edit carries notes on what is worth knowing about it, and while you type, the row above the input offers the command or earlier request you seem headed for. With a TypeSafe key, Jev weighs all three. See the user guide.

Where to go next

• The desktop: how Friday is driven, by the arrows and the mouse.
• User guide: sessions, modes and approvals, helpers, limits, troubleshooting.
• Configuration: every setting and variable.
• Tools: every tool the model can call.
• Editors and ACP: Friday inside Zed, JetBrains and other editors.