Using Junie in the terminal
Learn about working with Junie CLI in an interactive terminal interface.
Getting started
Once installed and authenticated, navigate to the project directory where you want to use Junie CLI.
Start an interactive session with Junie CLI.
junieType your prompt in the natural language.
> find the files in this project that handle log error descriptions
Real-time follow-up prompts
You can type follow-up prompts while Junie CLI is working on the task without waiting for it to finish. The added clarifications are appended to the initial prompt and taken into account by the agent immediately.
Slash commands and shortcuts
Slash commands allow you to access various Junie CLI features directly from the prompt. Type / in the prompt to see and use the available slash commands.
In addition to the built-in commands, you can add custom slash commands for frequently used prompts and repetitive tasks.
To see all available shortcuts, type ?.
Reference files and directories
Use @ to quickly reference files or directories in your prompt.
You can also drag and drop files and images into the terminal window to reference them.
Image inputs
Drag and drop or reference screenshots or design specs in the prompt for Junie CLI to read the image details. Junie CLI accepts all common image formats such as PNG and JPEG.
Search the prompt history
Junie CLI preserves your prompt history across all sessions and application runs.
To search the prompt history, use Ctrl+R, and then navigate through the results using Up and Down arrow keys.
Plan mode
In plan mode, Junie CLI analyzes the codebase with read-only operations and creates an implementation plan without making any changes to the project files.
To toggle plan mode, use the Shift+Tab shortcut.
Junie will suggest a plan and wait for the user input – either confirmation or rejection to proceed with the implementation. If you reject the plan, provide follow-up instructions to continue:
Faster results mode
Faster results mode speeds up Junie CLI on the fly while your prompt is being run. To enable faster results mode, use the Ctrl+F shortcut.
User approval
For running potentially sensitive actions, such as most of the terminal commands, code execution, or execution of MCP tools, Junie will ask for approval from the user.
You can authorize Junie CLI to execute all potentially sensitive actions without user approval by enabling brave mode with the Ctrl+B shortcut.
Managing sessions
Clear up session context
Use /new to clear up the context of the current session and start a new session in Junie CLI interactive mode.
Resume previous sessions
To see the session history and resume one of the previous sessions, use /history.
Junie CLI stores the full session context, including LLM usage data and the history of user prompts and agent responses, for the last 10 sessions.
Quit the session or logout
To exit the Junie CLI interactive mode without losing login credentials, use
/quit. Alternatively, you can exit Junie CLI by usingCtrl+Ctwice.To quit Junie CLI and log out of the current account, use
/logout.
View session transcript
To access the full transcript of the current session, including all previous prompts and the agent output, use the Ctrl+T shortcut. When in the Transcript view, use Ctrl+N to load older entries, or Esc to return to the main view.
Model selection
Use /model to select the LLM used for the current session. Default is the recommended pre-selected option that uses a dynamically set model with the best price quality ratio.
Token usage and costs
The /cost command shows the cost breakdown for the current session, including token usage, used models, and remaining balance.
Custom slash commands
Junie CLI supports custom slash commands that you can create to quickly execute frequently used prompts or repetitive tasks. Custom commands are added to the list of built-in slash commands that is shown when you type /.
To create a custom command:
Use
/commands→Create New Commandand provide the command name and description.Select the command scope:
Project-specific commands are stored as JSON files in the
.junie/commandsfolder at your project’s root directory. You can commit this folder to version control to ensure that all team members can use it.User commands are stored as JSON files in the
~/.junie/commandsfolder on your machine, making them available across all projects you open locally.
Enter and save the prompt.
To view, modify, or delete the added custom commands, use /commands.
Memory and guidelines
For user-defined instructions and project context, Junie CLI reads the .junie/guidelines.md file at the root of your project. The AGENTS.md open format for coding agents is also supported.
Junie CLI also checks for any guidelines or memory files from other AI agents when it opens the project for the first time. If such files are detected, it will suggest importing the instructions into .junie/guidelines.md.