A chat's side panel can hold your own terminal: a shell that opens in the chat's workspace folder, where you type commands yourself. It is yours alone: Oda does not type in it or read its output, and nothing from it joins the chat. The shells Oda keeps for its own commands are separate; see Persistent shells.
While a terminal starts, its tab reads Reading terminal environment…, then Starting…, then Connecting….
Reloading reattaches each terminal tab to its shell and restores the screen. If the shell is gone, for example after you quit Oda, the tab reads This terminal no longer exists. Open a new terminal. with a New terminal button that replaces the tab in place. Nothing restarts the old shell on its own.
Commands you type run with the rights of your own account on this computer, the same as a shell you open yourself. Oda never elevates them, and the chat's access mode, its approval prompts and Oda's sandbox do not apply to what you type; changing the access mode leaves the terminal as it is. Workspaces, files and permissions explains the modes.
The Start page of a chat's side panel shows a New terminal card; choosing it opens the shell you used last in the chat's workspace folder. For another one, use New tab in the panel.
The one you used last. The arrow beside New terminal lists the shells found on this computer and marks your remembered one; choosing a shell opens it right away, and it is remembered for later terminals.
The terminal comes from the Terminal tab switch under Settings > Developer > Advanced features. Switching it off removes the card and the tab at once; turn it on there. If your company manages the switch, ask your administrator. See Advanced features.
Yes. Collapsing the panel, switching tabs or chats, and floating or full-screen views leave the shell running, and a busy command is not stopped by a timer. The shell ends when you close its tab or quit Oda.
The tab disappears at once, and the app ends the shell and everything running in it, in the background. A closed terminal cannot be reopened, so open a new one when you need it. If the app cannot finish ending the processes, it remembers the request and tries again.
Reloading reattaches each terminal tab to its shell and restores the screen. If the shell is gone, the tab reads This terminal no longer exists. Open a new terminal. and offers a New terminal button; nothing restarts the old shell on its own.
A terminal that no open tab holds is closed after about two hours without activity. Only time in which the shell is definitely idle counts, so a command that keeps working is not reclaimed. A shell whose activity Oda cannot read as idle, such as PowerShell or fish, is not closed by this timer and may stay open; close its tab when you are done with it. Your installation can change the period or switch the automatic closing off. When a closing cannot finish, nothing tells you and there is no retry control; the terminal stays as it was.
Up to eight at a time, and exited terminals count toward the limit too. At the limit, a new terminal is refused with The terminal limit has been reached. Close unused terminals and try again. Exited terminals also count toward the limit. Close unused tabs to release them.
Only one view of a terminal owns the keyboard at a time; the other reads This view is read-only. with a Take control button. Choose Take control in the view you are working in.
A connection hiccup stopped the screen updates. The shell keeps running and the screen stays as it was; choose Reconnect to carry on. Commands are not replayed or stopped by the reconnection.
Typing is buffered up to 64 KiB at a time, and a very large paste can overflow the buffer. The tab shows a note reading The input buffer is full. Reconnect and try again. Choose Reconnect, then carry on.
No. Commands you type run with the rights of your own account on this computer, and they are not checked by the chat's access mode or by Oda's approval prompts. Nothing widens your rights for them. Workspaces, files and permissions explains the modes.