CodeNeterInteractive use
Work with the agent in a terminal session, switch modes and models, handle approvals, and resume earlier sessions.
Run codeneter in a project to open an interactive session. You describe tasks at the prompt, and the agent's replies, tool activity, and file changes stream into the terminal as it works.
Reading responses and long prompts
Replies render Markdown as they stream, including headings, lists, tables, and code blocks.
Long submitted prompts appear as a compact preview. Ctrl+O expands or collapses long messages and tool output. This only changes the display: the complete prompt is still sent to the model and saved in the session. Submitting a new prompt returns the display to its collapsed state.
When live output is taller than the available space, use Page Up/Page Down or Ctrl+U/Ctrl+D to scroll it.
Modes and models
Switch modes with /mode agent, /mode plan, or /mode ask. Planning and modes explains when to use each. In Plan mode, the CLI shows the finished plan and asks whether to implement it or keep revising.
/model switches to another model or back to Auto. To start a session with a particular mode or model, pass --mode or --model.
Context and shell commands
Type @ to mention a file or folder in the project.
Start a line with ! to run a shell command yourself in the project folder, for example !git status. The output appears in your terminal but isn't sent to the agent.
Use /compact to summarize a long conversation and free up context. See Context and compaction.
Approvals
When an action needs approval, the CLI asks before running it:
| Choice | Effect |
|---|---|
| Run once or Approve once | Allows this action only |
| Run everything this session or Approve everything this session | Turns off confirmations for all actions in this conversation |
| Skip | Refuses the action; the agent continues without it |
/yolo toggles auto-approval for the conversation. This choice is saved when you resume and carried over by /clear and /delete-chat. Turning it off returns to your configured defaults; if autoApprove is true there, actions still run without confirmation.
A few inspection commands, such as ls, find, and git status, run without asking, even with options that change files, such as find -delete.
Stop, clear, and resume
Ctrl+C stops the current response or shell command. /clear starts a new conversation, and /exit quits.
Sessions are saved on your computer. When you quit, the CLI prints the command to pick up where you left off:
codeneter --resume=<session-id>Inside a session, /resume lists recent sessions for the current folder. CLI sessions are separate from desktop app conversations.