Intro

Fring is an AI coding agent. It’s available as a terminal-based interface, desktop app, or IDE extension.

Let’s get started.

---

Prerequisites

To use Fring in your terminal, you’ll need:

1. A modern terminal emulator like:

   • WezTerm, cross-platform
   • Alacritty, cross-platform
   • Ghostty, Linux and macOS
   • Kitty, Linux and macOS

2. A Fring account. Models are included, so there are no provider API keys to collect — you sign in once, in Configure below.

---

Install

The easiest way to install Fring is through the install script.

curl -fsSL https://fring.ai/install | bash

You can also install it with the following commands:

• Using Node.js

  npm

  npm install -g @fring.ai/fring

  Bun

  bun install -g @fring.ai/fring

  pnpm

  pnpm add -g @fring.ai/fring

  Yarn

  yarn global add @fring.ai/fring

Windows

Recommended: Use WSL

For the best experience on Windows, we recommend using Windows Subsystem for Linux (WSL). It provides better performance and full compatibility with Fring’s features.

• Using PowerShell

  irm https://fring.ai/install.ps1 | iex

• Using NPM

  npm install -g @fring.ai/fring

---

Configure

Fring reaches models through Fring Zen, our metered gateway. There are no provider API keys to collect — you sign in once and the agent is configured.

fring login

That prints a URL and a short code, opens your browser, and waits. Approve it there and the CLI finishes on its own.

You can also sign in from the TUI with /connect, or from the desktop app’s sign-in screen. All three write the same credentials, so signing in on one surface covers the others.

To confirm which account, workspace and plan you are on:

fring console status

The Free plan needs no card on file. See Providers for the model catalog and how to choose one, and Zen for the gateway itself.

Note

On a signed-in account, direct provider credentials are ignored — the console sends an allowlist and the engine drops anything not on it. Setting ANTHROPIC_API_KEY or OPENAI_API_KEY will not add a provider to the picker.

---

Initialize

Now that you’ve configured a provider, you can navigate to a project that you want to work on.

cd /path/to/project

And run Fring.

fring

Next, initialize Fring for the project by running the following command.

/init

This will get Fring to analyze your project and create an AGENTS.md file in the project root.

Tip

You should commit your project’s AGENTS.md file to Git.

This helps Fring understand the project structure and the coding patterns used.

---

Usage

You are now ready to use Fring to work on your project. Feel free to ask it anything!

If you are new to using an AI coding agent, here are some examples that might help.

---

Ask questions

You can ask Fring to explain the codebase to you.

Tip

Use the @ key to fuzzy search for files in the project.

How is authentication handled in @packages/functions/src/api/index.ts

This is helpful if there’s a part of the codebase that you didn’t work on.

---

Add features

You can ask Fring to add new features to your project. Though we first recommend asking it to create a plan.

1. Create a plan

   Fring has a Plan mode that disables its ability to make changes and instead suggest how it’ll implement the feature.

   Switch to it using the Tab key. You’ll see an indicator for this in the lower right corner.

   <TAB>

   Now let’s describe what we want it to do.

   When a user deletes a note, we'd like to flag it as deleted in the database.
   Then create a screen that shows all the recently deleted notes.
   From this screen, the user can undelete a note or permanently delete it.

   You want to give Fring enough details to understand what you want. It helps to talk to it like you are talking to a junior developer on your team.

   Tip

   Give Fring plenty of context and examples to help it understand what you want.

2. Iterate on the plan

   Once it gives you a plan, you can give it feedback or add more details.

   We'd like to design this new screen using a design I've used before.
   [Image #1] Take a look at this image and use it as a reference.

   Tip

   Drag and drop images into the terminal to add them to the prompt.

   Fring can scan any images you give it and add them to the prompt. You can do this by dragging and dropping an image into the terminal.

3. Build the feature

   Once you feel comfortable with the plan, switch back to Build mode by hitting the Tab key again.

   <TAB>

   And asking it to make the changes.

   Sounds good! Go ahead and make the changes.

---

Make changes

For more straightforward changes, you can ask Fring to directly build it without having to review the plan first.

We need to add authentication to the /settings route. Take a look at how this is
handled in the /notes route in @packages/functions/src/notes.ts and implement
the same logic in @packages/functions/src/settings.ts

You want to make sure you provide a good amount of detail so Fring makes the right changes.

---

Undo changes

Let’s say you ask Fring to make some changes.

Can you refactor the function in @packages/functions/src/api/index.ts?

But you realize that it is not what you wanted. You can undo the changes using the /undo command.

/undo

Fring will now revert the changes you made and show your original message again.

Can you refactor the function in @packages/functions/src/api/index.ts?

From here you can tweak the prompt and ask Fring to try again.

Tip

You can run /undo multiple times to undo multiple changes.

Or you can redo the changes using the /redo command.

/redo

---

Customize

And that’s it! You are now a pro at using Fring.

To make it your own, we recommend picking a theme, customizing the keybinds, configuring code formatters, creating custom commands, or playing around with the Fring config.