Start your first session
A Localix session keeps a conversation, agent configuration, and access to a working folder. This walkthrough connects a model, opens a project, runs one bounded request, and shows you where to inspect it.
Terminology
| Term | Meaning here |
|---|---|
| Session | A persisted transcript and runtime configuration for one stream of work. |
| Project | A Localix record for a working directory and shared project settings. |
| Provider connection | Saved configuration and credentials for a model provider. |
| Agent | The instructions plus capability rules that decide what a run may use. |
What you can do
| Action | Mechanism | Boundary |
|---|---|---|
| Connect a model | The composer's model picker stores a provider connection and model selection. | A saved connection is not proof of a live model response. |
| Open a folder | Add project folder creates or selects a project whose working directory is that folder. | Project selection does not copy or isolate the folder. |
| Start work | Your first message creates or reuses a session for the selected project. | A model request needs a usable provider connection and model. |
| Inspect a change | The transcript shows tool activity; Source Control opens repository changes. | Source Control appears only when the working directory is a Git repository. |
| Correct an active run | A follow-up message enters the session's backend queue. | Text can steer at a safe boundary; attachments remain queued for a later turn. |
How it works
- Install and launch Localix with your chosen desktop or source workflow.
- Open the model picker under the chat composer, connect a provider with an API key or sign-in, and choose a model. The providers guide covers connections.
- Select Add project folder and choose a disposable repository or confirm that
git statusis clean before using a mutating example. Selecting a previously added directory switches to its existing project. - Check the model selector for the new conversation. Select a usable connection and model if the conversation has no resolved pair. Agent or session choices can take priority over project defaults.
- Send a request with a small, visible outcome. For example: “Add one sentence to the installation
section in
README.md, then show me the diff.” - Read the transcript as tools run. Open Source Control to inspect the resulting Git diff; use the workspace guide for the editor, terminal, preview, and diff surfaces.
- If the run heads in the wrong direction, send a short text correction. The backend gives user messages priority over internal wake work and retains queued items across reconnects.
Use Attach file or drop material into the composer when your request needs a document or image. The attachment guide explains stored uploads, original paths, previews, and format limits.
Configuration
| Control | What it changes | Boundary |
|---|---|---|
| Model selector | The connection and model for the conversation. | The saved connection must still exist. |
| Agent | The agent you pick when you start the conversation. | Available tools depend on the agent's effective policy. |
/help | The built-in command list and command-specific help. | Plugin, mini app and surface-specific commands add to this catalog. |
The capabilities guide owns policy details. The commands guide owns the current slash-command catalog. Use Sessions and projects for the queue, interruptions and what the agent sees, and Subagents to run work in parallel.
Limits
- A saved provider connection does not prove that a model request will succeed.
- A project records a working directory. Sessions using the same project can act on the same files by default.
- Queued text is delivered only at a safe runtime boundary. Pending human input, attachments, and control operations can delay delivery.
- Capability and permission rules gate Localix tool calls. They do not provide process, filesystem, or network isolation.
- Model calls and enabled network tools can send data off the machine. Review Localix data flow before using sensitive material.