Conversations and Terminal Sessions

The right pane supports built-in conversations and terminal sessions. Start with the built-in Conversation Agent; use a terminal when you want a CLI you already know.

Built-in conversation

Configure Settings → AI Agent → Models, select a default model and start a conversation. Ask about a document you opened, inspect sources, and save useful results to the project. Model availability and cloud billing belong to the provider you configured.

Optional terminal

A terminal session runs real commands and can launch Claude Code, Codex or another configured CLI. The CLI uses its own authentication and permissions. Scholardo's file-tool path checks do not sandbox arbitrary commands.

See Agent & MCP Tools for project access. You do not need this setup to use the built-in agents.

Sessions and model choice

Separate sessions keep separate conversation contexts. Choose the right model for the session and verify which provider is serving it. Starting a different CLI is different from choosing a model for an existing built-in conversation.

Closing a session is not the same as deleting project files. Saved drafts remain in Workspace, and session history can be searched from the right pane. Keep important conclusions in reviewed project files rather than relying only on a transcript.

Voice input

Where configured, the composer can transcribe microphone input using your selected speech service. A cloud speech service receives the audio it processes; voice input is not covered by a claim that local text generation stays on-device. Check the service configuration before dictating confidential material.

What to try first

Read one PDF and save a reviewed note. For file and command permissions, see Data flows.