Settings Reference
Match each Settings menu entry to practical steps and detailed tutorials.
Open: avatar or Nexts logo menu in the activity bar → Settings.
Configure only what you need. The index below follows the Settings menu entry by entry. Sign-in, subscriptions, usage, and device management are covered in Account & Usage.
Find a setting
General
Choose the preferences you need, then verify them in a new conversation:
| Setting | How to use it |
|---|---|
| Language and time zone | Choose a UI language; let the calendar follow the system zone or select a fixed zone |
| Sending messages | Choose Enter or Ctrl+Enter and check line-break behavior before typing long messages |
| Startup and closing | Configure autostart, minimized startup, and whether closing exits, asks, or keeps Nexts in the tray |
| Notifications | Enable message, calendar, or task notifications as needed; check OS notification access |
| Keep awake | Enable for long-running work; the display can still turn off according to system settings |
Keeping Nexts in the tray leaves it running. Scheduled tasks and remote access require the host app to remain active.
Appearance
Choose light, dark, or system theme, then adjust fonts and UI text size. Check a long conversation for readability. Editor and terminal appearance have separate development settings.
Keyboard shortcuts
- Search for an action or find it under global, conversation, or navigation shortcuts.
- Select edit and press a combination with a modifier. Valid combinations without conflicts are saved; press Esc to leave recording.
- Test in the relevant context, including another foreground app for global shortcuts.
Choose another combination if a conflict appears. If nothing happens, check OS, input-method, and other app bindings. Removing a binding affects that combination. Resetting defaults requires confirmation and affects the current operating system's shortcuts.
Model services
Configure official, custom API, or local models. Save, refresh the list, and choose a model in chat. See model setup.
Agents
Manage local, SSH, and custom ACP agents and inspect installation, authentication, and connection status. Follow Agents & Assistants. A successful handshake still needs a real conversation to verify model availability.
Assistants
Create roles with a default agent, tools, skills, memory, and approval settings, or organize a group. See assistant setup. Use Bots for persistent spaces with independent material and memory.
Memory
User memory holds stable preferences; project memory holds workspace conventions. Manage Bot memory in Bot details. Automatic capture may save directly, and disabling it does not erase entries. See memory management for adding, verifying, and removing records.
Editor
Adjust code display, indentation, autosave, and formatting. File detection can override default indentation; formatting needs language support. See Editor, Terminal, and Git.
Terminal
Choose a default shell and adjust display and scrollback, then open a new terminal to verify. Existing sessions keep their shell. See terminal setup.
Workspace & Git
Configure filename filtering, hidden files, automatic Git refresh, and diff display. These settings do not commit or push code. See development settings for their scope and verification steps.
Web search
Select official or custom search and test it after saving. Search and model credentials are separate. See web search.
Media services
Choose microphone, system audio, transcription engine and language, summary model, and available voice options. Availability depends on your platform, installed components, and account.
Test a short recording before a meeting. Cloud transcription or voice sends the necessary audio to the selected service. See Voice & Video for available features and meetings for recording steps.
Remote access
Manage the service, LAN access, phone pairing, and remote desktop. The current phone QR uses m.nexts.ai; it does not require the older public tunnel. Follow remote access.
Security center
Check Python, Node.js, and Git Bash availability, source, and location under Built-in runtime. Install missing components through the available controls, then inspect the status again. Refreshing can also prepare or update the bundled runtime.
Some security cards and disabled controls currently display status; this page does not edit every file, command, or network rule. Choose task approval modes in the chat composer and manage external agent, plugin, and account access in their own entries. See permissions.
Data
Inspect data, workspace, mini app, plugin, and log locations and usage. Open a folder to locate files. Preserve important material before migration, follow the restart prompts, and verify reading and writing afterward. See Data, Migration & Archives.
Clearing all conversations permanently deletes conversation records and cannot be undone. Use archiving to tidy the list.
Archived conversations
Find a record, restore it, and return to the chat list. Archiving retains records; permanent deletion cannot be undone by restoring an archive. See archive and deletion scope.
Mini & Pets
Enable the floating bar and desktop pet independently, select a character or import Petdex, and view task-status bubbles. See Mini Bar & Desktop Pets. These features require the desktop client.
Logs & diagnostics
- Note the issue's time, current version, and reproduction steps.
- Adjust the log level if troubleshooting requires it, then reproduce once. Keep the default level for ordinary issues initially.
- Open the dated log directory, or select Export diagnostics and confirm.
- Locate the ZIP, inspect its contents, and share it manually with support together with reproduction steps.
The bundle includes recent logs, run records, and crash information. Exporting does not send it automatically. Logging controls require the desktop client.
Sensitive debugging can include conversations, model requests, and tool arguments. Turn it off after troubleshooting; old logs remain. Review the bundle before sharing.
About
Note the installed version, select Check for updates, review release information, and follow the download or installation prompts. Save active work before restarting, then verify the version here. Include version, OS, and reproduction steps in support reports.