↳ BUILT FOR THE WORK BEYOND THE PROMPT.LOCAL-FIRST / MODEL-DIRECTED
01 THE WORKSPACE
A conversation is only the beginning.
A question becomes a calculation. A calculation becomes a file. VARIANT-1 brings code, browsing, and desktop tools into the same conversation, with working data ready for the follow-up.
From an open question to something that works.
Explore a codebase, clean a dataset, or write a script. Run it, check the output, and reuse the working data when you ask for a change.
FILES → CODE → CHECKED OUTPUT
Follow the evidence. Keep the thread.
Compare documents, gather sources, and analyse what you find. Keep references and working notes together as the question develops.
SOURCES → SYNTHESIS → FOLLOW-UP
From a file to the app you use.
Prepare a file, open it in a supported application, and check the result. Give corrections from the same conversation.
FILES → BROWSER → APPLICATIONS
VARIANT-1 / MAIN DECKDEVELOPMENT INTERFACE
One workspace. Room for the whole task.Development UI · sample data · September 2026
Development preview with sample data. The interface may change before the public beta.
02 THE METHOD
Keep the state. Change the approach.
Let your model work through a task in Python, combine tools, and adjust its approach as it goes.
STRUCTURE / VARIATION
ONE SYSTEM. MANY POSSIBILITIES.01 → 02 → 04
01 /
Keep the work ready to continue.
Each chat has a live Python environment. Variables, imports, and helper functions stay available between calls, ready for the next step.
02 /
Tools that work together.
Use code to connect the steps: read a file, transform its data, call a tool, and check the result. Keep useful operations as reusable helpers.
03 /
Room to adapt. You stay in the loop.
With mutation enabled, your model can revise tool methods within the chat. Review the output, give a correction, or stop the run.
ADAPT THE METHOD. RETAIN THE USEFUL WORK.Mutation is optional · Off by default
03 MODEL CHOICE
Your model. Your call.
Local models or cloud access. Choose what fits the task.
Run a supported model on your Windows machine. Bring the model files and hardware it needs.
LOCAL MODELS
↗
Connect an API key
Use your provider API key or a supported custom endpoint. Model usage is billed by your provider.
API KEYS + CUSTOM ENDPOINTS
⊕
Connect an account
Sign in through a supported provider connection. Your account must include the access that provider requires.
SUPPORTED ACCOUNT CONNECTIONS
04 GOOD QUESTIONS
A few things worth knowing.
PATTERNS / POSSIBILITIES
Is VARIANT-1 free?+
The Windows beta will be free to download, with no VARIANT subscription. You bring a local model or your own cloud access. Any provider charges, subscriptions, and usage limits still apply.
Can I download the Windows app?+
Not yet. The public beta is in preparation. The Windows installer and setup instructions will appear on the release page when they are ready. Read the release status ↗
Does everything stay on my computer?+
The app and its Python environment run on your computer. If you choose a cloud model, relevant messages and tool results go to that provider. Browsing and connected services also use the network, even with a local model.
What does “persistent” mean?+
Python variables, imports, and helpers stay available while the chat’s runtime is alive. Restarting or losing that runtime can clear them. Optional checkpoints can preserve supported values, but checkpointing and restoration are off by default and do not restore every live object or connection.
What changes when tools mutate?+
Mutation lets the model revise executable tool methods within a chat. It is off by default and does not train the model. A changed method still needs checking against the task. Turning mutation off stops new changes; existing active changes are not erased.
Is it open source?+
Yes. VARIANT-1’s source is available as an early preview under the MIT License. Third-party components retain their own licenses. A public Windows installer is still in preparation. View source ↗