Interactive Mode (Build)
The default interactive mode (bytemind) is the primary way to use ByteMind — known as Build mode. It supports multi-turn conversations, persistent context, and dynamic task adjustment. bytemind chat still works as a compatibility alias.
bytemindHow It Works
When you start chat mode, ByteMind:
- Resolves the current directory as the workspace
- Loads the global user config (
~/.bytemind/config.json) first, then merges the workspace.bytemind/config.jsonon top (overriding same-name fields) - Initializes or resumes an existing session
- Enters interactive mode and waits for your input
After you describe a task, the agent calls tools (read files, search code, run commands) to complete it. High-risk tool calls pause and wait for your approval.
Startup Options
| Option | Description | Default |
|---|---|---|
-config <path> | Custom config file path | auto-detected |
-max-iterations <n> | Max tool-call turns per task | 64 |
-workspace <path> | Workspace directory | current dir |
-v | Verbose/debug output | false |
Examples:
bytemind
bytemind -max-iterations 64
bytemind -config ~/.bytemind/work.json
bytemind -workspace ./my-projectBest Practices
State your goal and constraints upfront
Tell the agent what outcome you want and what it should not touch:
Add email format validation to UserService. Only change the service layer — do not modify the interface or tests.Work in small verifiable steps
For large tasks, break work into checkpoints and confirm each one before proceeding:
First just read the relevant files and analyze the current implementation. Do not make any changes yet.Activate skills to accelerate specific workflows
Built-in skills significantly improve output quality for targeted scenarios:
/bug-investigation symptom="order creation endpoint occasionally returns 500"
/review base_ref=main
/repo-onboardingSwitch modes for complex tasks
When a task needs phased execution, switch to Plan mode:
/plan
Split the HTTP handler layer into a dedicated controller package. Show me the plan in stages.Session Command Reference
| Command | Description |
|---|---|
/help | Show all available commands |
/session | Open session picker to view/resume/delete sessions |
/new | Start a new session |
/plan | Switch to Plan mode |
/build | Switch back to Build mode |
/model [provider/model] | Switch model or open the interactive picker |
/models | Show current model and all discovered models |
/agents [name] | List subagents or show one definition |
/explorer | Show the builtin explorer subagent |
/review | Show the builtin review subagent |
/commit <message> | Stage all current changes and create a local Git commit |
/undo-commit | Undo the last local commit created by /commit in this session |
/quit | Exit safely |
For /commit, choose the command from the slash palette or type it directly, then provide the commit message yourself:
/commit fix(/commit): improve commit feedbackByteMind stages the current workspace changes with git add -A before committing, then reports the commit hash, message, and file count.
Use /undo-commit only for the previous commit created by /commit in the same session. It is blocked when that commit has already reached the upstream branch, when you are in a different session, or when newer working tree changes would be mixed into the undo.
Interrupting and Resuming
Press Ctrl+C or type /quit at any time — the session context is automatically saved.
To resume later: start bytemind, enter /session, select the previous session in the picker, and press Enter.