Documentation

Everything you need to run Refinix.

Refinix is a private agent workbench: chat, documents and code, running on your own computer. Nothing you type or attach leaves the machine. This page covers getting it running, using it day to day, and what this pre-release build genuinely cannot do yet.

Getting started

Refinix runs entirely on one computer. There is no account to create, no key to paste and no service to sign up for — which also means the machine you install it on is the machine that does the thinking.

What you need

A computer you control
Windows, macOS or Linux. The work happens locally, so a machine with more memory answers faster.
A local model engine
Refinix talks to an engine on your own machine over 127.0.0.1 — Ollama on its default port is the usual choice. Refinix does not ship the model; you choose it.
At least one open-weight model
Any chat model the engine has pulled. Smaller models answer faster; larger ones answer better. You can switch at any time.
No internet connection
Not a requirement — the point. Once the model is on the machine, Refinix works with the network unplugged.

First run

  1. Get the build Download it from the download section and check it against the published checksum. Refinix is Apache-2.0, so you can also build it from source.
  2. Open Refinix and let it look around On first launch it checks this computer for a model engine and reports what it found. The line at the bottom-left of the window is the short version — Ready on this computer means the engine answered and a model is installed.
  3. Check the engine in Settings Open Settings from the bottom of the sidebar. AI engine and model names the engine it reached, the model in use and any others available. If it says the engine did not answer, start the engine and press Re-check now.
  4. Ask your first question Go back to Chat, type into the box at the bottom and press Enter. The first answer from a cold model is always the slowest — it has to be loaded into memory before it can reply.
How to tell it is really local

The address bar says 127.0.0.1. That is your own machine and nothing else can reach it. Settings → Advanced shows the exact engine address Refinix is talking to, so you can confirm rather than take our word for it.

User manual

Everything below describes the running application. If a control is named here in bold, that is the word printed on it in the window.

The window

Refinix is one window in three columns. Both side columns fold away with the two buttons at either end of the header, so the conversation can have the whole width when you want it to.

  1. Sidebar. The Chat / Code switch sits under the logo, your conversations below it, and Settings at the bottom.
  2. Header. The surface name, the state of the current request, the light/dark button, and a fold button at each end for the two side columns.
  3. Message box. Where you type. Everything you can attach to a request lives here too.
  4. Details. A live record of the request that is running: the stages it passed through, the attempt, and the events as they arrive. Safe to ignore; useful when something looks wrong.

The round button in the header switches between light and dark. The icon shows the theme that is on — a moon and star while dark, a sun and cloud while light — and the choice is remembered.

Chatting

Type into the box at the bottom and press Enter to send. Shift + Enter starts a new line instead, so you can write a paragraph without sending it half-finished.

  • While it is working the mark beside the box turns and the header says the request is running. A Stop button appears next to Send — pressing it ends that reply and keeps everything already written.
  • The model button at the bottom-right of the box names the model answering. Click it to switch to another model the engine has installed.
  • Scrolled up mid-answer? A small arrow appears over the conversation; click it to jump back to the newest text. Refinix will not yank the view down while you are reading.
  • Your draft is kept. If you type something and switch conversations, the half-written message is still there when you come back.

Managing conversations

The sidebar lists every conversation on this computer, newest first.

  • + New conversation sits at the top of the list, above your history, so starting fresh never means scrolling.
  • The magnifier beside the word Conversations opens a search box. It searches titles and message text; closing it puts the full list back.
  • The … on a row opens the actions for that conversation — renaming and pinning among them.
Conversations are files on your disk

They are stored on this computer and nowhere else. That also means they are yours to back up — and that deleting one is permanent.

Files and documents

The + button at the bottom-left of the message box attaches files to a request, or picks a document skill. You can also drag files onto the message box.

Reads today
txt, md, csv, json as plain text, and docx Word documents.
Writes today
docx.
Per request
Up to 10 files, 20 MB each.
Searching documents
Keyword search — it matches the words you type, not their meaning. No embedding model is installed, and the product labels this rather than implying more.
Plain chat does not read your attachments

Attaching a file to an ordinary chat message does not make the model read it. Choose a document skill with + to have the files on that request actually read. This is deliberate: nothing is fed to a model without you asking for it.

Changing code

The Code surface edits files in a project folder you choose. The order is always the same: pick the folder, pick the files that may change, describe the change, then read the diff.

  1. Choose a project Choose project above the message box picks the folder. Nothing outside it is ever read or written.
  2. Select the files Use + to pick the files that are allowed to change. Refinix sends the minimum set — not the repository.
  3. Describe the change and press Propose You are asking for a proposal, not an edit.
  4. Read the complete diff, then approve Every line that would change is shown before anything is written to disk. Nothing is saved until you say so.
Not available in any access mode

Refinix replaces the contents of existing text files you select. Creating, deleting or renaming files, running project commands, using Git, and installing anything are not available — not gated behind a setting, not present.

How much it remembers

A model can only consider so much text at once. That budget is the context window, and Refinix divides it between the conversation it sends and the room it leaves for the reply. You can see the exact split in Settings → Advanced → Conversation limits, drawn as a single bar.

  • When a conversation gets long, older complete exchanges are left out of the next request so it still fits.
  • Your saved history is never changed. Leaving an exchange out of one request does not delete it — scroll up and it is still there.
  • The meter beside + shows how full the current request is, so a long conversation is visible before it becomes a surprise.

Settings and Advanced

Settings answers one question per card: is this computer ready, is the engine ready, is anything else connected, and is anything running right now.

Advanced is collapsed by default and nothing in it is needed for ordinary use. It opens with three charts of what this computer has actually been doing — how long replies take, which hours it was busy, and how requests ended — followed by the engine address, model settings, the token window, addresses and the recent job record.

A hatched value means "not observed"

Where a row is struck through with diagonal lines, Refinix has no evidence for it — not a failure, and never to be read as a healthy zero. The work that would produce that evidence has not run.

Limits & answers

This is a pre-release build. The honest list of what it will not do is shorter to read than finding out the hard way.

Not in this build

PDF files
Not read. A reviewed PDF text adapter has not landed yet.
Scans and photographs of text
Not read. There is no OCR in this build, and Refinix will not guess at words in a picture.
Meaning-based document search
Not available — search matches words, not meaning.
Creating, deleting or renaming files
Not available on the Code surface in any access mode.
Running commands, Git, installing packages
Not available.
Sharing work with another computer
Pairing is shown in Settings but no worker is paired yet.

Common questions

Does anything I type leave my computer?

No. Refinix binds to 127.0.0.1, which is the machine itself, and it talks to a model engine on that same machine. Unplug the network and it keeps working.

The website you are reading runs no inference and stores no chats either.

Which models can I use?

Any chat model your local engine has installed. Refinix does not ship a model and does not restrict you to a list — the model button in the message box shows what is available on this computer and switches between them.

Why is the first answer so slow?

The model has to be loaded into memory before it can reply. That happens once; later answers in the same session are faster. Settings → Advanced shows whether a model is currently resident, and the reply-time chart shows what is typical on your machine.

Can I trust what the model tells me?

Treat it as a capable assistant, not an authority. Refinix is careful about its own claims — every state it reports is something it observed, and it marks anything it has not observed rather than filling the gap. It cannot make the same guarantee about the model's prose, so check anything that matters.

What happens to a request if I close the window?

Work that was interrupted is reconciled the next time Refinix starts, and the count of repaired requests is reported in Settings → Advanced. Nothing is left claiming to be running when it is not.

Where is my data kept?

On this computer, in Refinix's own workspace. Settings → This computer names the location, and conversations, drafts and job records all live there.

Something here wrong, or a question this page did not answer? Refinix is Apache-2.0 and developed in the open — corrections to the documentation are as welcome as corrections to the code.