Panes and splits

On this page, mod means ⌘ Command on macOS and Ctrl on Windows and Linux.

The new pane takes half of the space the focused pane had, and it gets focus. Both commands are also in the Command Palette (mod+K).

As a pane gets narrower, its header gives things up in this order. Below about 360 pixels the folder, shell and worktree labels shrink to icons, and the pane's title stays. Then the buttons go one by one: split down, split right, the Control Room (formerly War Room) button, the Chat | Terminal switch and the share globe, in that order, and the broadcast button last (it shows only during a broadcast). Close Terminal Pane always stays visible, and so does Maximize Pane while the pane is not maximized, and the keyboard shortcuts work at any width. On a maximized pane, or a pane brought to the middle, Restore Pane also shows past the close button, at any width.

• Drag the divider between two panes. A pane cannot be made smaller than 40 pixels.
• If you release the divider within 3.5% of the middle, it snaps to an even 50/50 split. While you drag inside that range, the divider shows a 50% : 50% badge.
• Double-click a divider to set that split back to 50/50.
• Equalize Panes, in a pane's right-click menu, evens out every split in the tab at once. Its shortcut is mod+P, which you can rebind in Keyboard shortcuts; it is also in the Command Palette.

• Click a pane to focus it. The focused pane has an accent-coloured border, and the other panes are dimmed. A pane that is alone in its tab is never dimmed.
• Press Ctrl+Tab to open Quick Terminal Switcher, a list of every pane in every tab, with the next pane selected. Keep Ctrl held and press Tab again to move down or Shift+Tab to move up, then release Ctrl to jump to the selected pane. You can also click an entry. This shortcut uses Ctrl on macOS too.
• To move between tabs, see Keyboard shortcuts.

Give a pane a name of your own. Right-click the pane and choose Rename pane…, or double-click the pane's row in the Terminals list of the left sidebar. Press Enter or click away to save, press Esc to drop the change, and leave the field empty to remove the name. A name is at most 40 characters. A phone paired with this computer can rename a pane that is shared with it from the session screen, with the same rules; it needs no permission to type.

The name is saved with the layout. It shows in the pane header, in the sidebar list and in the Quick Terminal Switcher, and it is the name the pane has in a Control Room. In the pane header and in the sidebar, a title that is cut off shows in full when you hover it. On the pane's row in the sidebar's Terminals list, the second line also shows the git branch of the pane's folder, only when one is known; it is cut first when the row is narrow. It is not shown for SSH panes. Double-clicking the header does not rename the pane. It brings the pane to the middle of the window, see Bring a pane to the middle.

Drag a pane by its header bar. Start the drag on an empty part of the header, not on a button or picker.

The program running in a pane keeps running when you move or swap the pane, whether it lands in the same tab or another one. A tab that is still on the composer has no panes yet, so you cannot drop a pane into it.

You can also drag a whole tab onto a pane. Aim at an edge of the target pane and the dragged tab's layout is inserted beside just that pane; aim at the outer band of the pane area and the two tabs' layouts are joined side by side. The centre of a pane does nothing for a tab drag, because a tab cannot swap places with a single pane. Two tabs can only be merged when they are compatible: either both SSH tabs on the same host or neither an SSH tab, and either both isolated in git worktrees of the same folder or neither isolated. When they are not, the menu row says why.

The pane's right-click menu has the same moves without a drag: Move Pane to New Tab, Move Pane to Tab with a submenu of the other tabs, and Swap With Pane…, which turns every other pane into a click target. A tab's right-click menu has Merge Into.

A tab can live in a window of its own. Everything in it keeps running through the move: the panes are not restarted, and each terminal reattaches to the same process with its scrollback intact.

Closing a window that still has terminals asks first: Close this window? offers Cancel, a button that closes the terminals (Close 3 terminals, with the real count), and, when another window can take them, Move tabs to main window or Move tabs to the other window. A window with no terminals left just closes, and closing the last window quits the app.

A share you started on a pane stays on when you move its tab to another window, because it belongs to the pane's terminal and not to the window. The share button and the Remote Access & Devices page in Settings follow a change in every open window.

Double-click a pane's header to bring that pane to the middle of the window. The pane is drawn over the others at about 80% of the window's width and height, and the rest of the window is dimmed and blurred behind it. One pane can be in the middle at a time. It is only a way of looking at the pane: the layout does not change, and the view is not saved. Bring to the middle is offered only when the tab has two or more panes.

To put the pane back, click the dimmed area outside it, double-click its header again, or click Restore Pane, the − button at the far right of the header, past the close button.

If you maximize a pane that is in the middle, restoring it returns it to the middle first, and a second restore puts it back in the layout.

Maximizing makes one pane fill the window and hides the other panes of the tab behind it. These maximize it:

• mod+Shift+M for the focused pane.
• Maximize Pane in the pane header.

While a pane is maximized, the Maximize Pane button is replaced by Restore Pane, the − button at the far right of the header, past the close button. To restore the pane, click it, press mod+Shift+M, or double-click the header.

Esc does not restore a maximized pane. Use one of the actions above.

If you click the close button on a maximized local pane, or on a local pane in the middle, the app asks Close this pane? and offers Un-maximize instead. A pane from another MXterm closes at once. mod+W closes any pane without asking.

• Press mod+W to close the focused pane, or click Close Terminal Pane in the pane header.
• Closing a pane ends the program running in it.
• Closing the last pane of a tab closes the tab.

Broadcast sends what you type in one pane to every pane in its group. It works within the current tab. The broadcast button is the radio icon next to Workspaces in the sidebar.

1. Press mod+Shift+B. Broadcast turns on and every pane in the tab joins the group.
2. To leave a pane out, hold ⌥ Option (Alt on Windows and Linux) and click it. The same gesture adds it back. While broadcast is on, each pane header also shows a broadcast button that does the same.
3. Type or paste in any pane of the group. Each pane receives the input and runs it in its own session. Panes outside the group are faded, and typing in one of them stays in that pane.
4. Press mod+Shift+B again, or Esc while a terminal has focus, to turn broadcast off. The group is cleared, so turning broadcast on again adds every pane back.

Chat view shows an agent's conversation as readable messages instead of terminal text. It is experimental and off by default. Turn it on with Chat view (experimental) in Settings → Terminal.

• It supports Claude Code, Codex, omp and Grok, and reads the conversation from the agent's own transcript file. It is not available on SSH panes. If no supported agent is running in the pane, or it has not written its conversation file yet, the pane says so and offers Back to terminal.
• With Chat view on, a pane header has a button, Show as chat or Show terminal. mod+Shift+J does the same for the focused pane, and you can rebind it in Keyboard shortcuts.
• Chat covers the terminal and does not replace it. The terminal and its program keep running underneath, and switching back shows them as they were. Turning Chat view off in Settings puts every pane back on its terminal.
• The box at the bottom sends your message into the same pane: Enter sends and Shift+Enter adds a new line. When the agent asks for permission, the question appears above the box with Approve once and Reject and stop the agent. If the agent is waiting for an answer that cannot be given there, the chat offers Open terminal.
• mod+↓ scrolls the focused pane to the bottom and puts the keyboard in its input: the chat box when the pane shows Chat, the terminal otherwise.
• A pane shared from another MXterm can show as chat too, when the host runs a version that supports it. If the host shared the pane as view only, you can read the chat but not send from it.

When an agent in a pane stops to ask you something, a card appears at the bottom of the pane in Terminal view. It appears for a Claude Code question with 2 to 9 options and one answer, and for a permission prompt from Claude Code or Codex. It does not appear for a question with several parts or several answers, or for a free-text question from Codex or Gemini. Click an option to answer without typing in the pane, or use Other to type your own answer. In Chat view, the chat's own prompt bar asks instead. On a permission prompt the card shows every answer the prompt offers, such as switch to auto mode, wraps a long label instead of cutting it, and marks the answers that stay in effect after this one.

A paired phone can answer the same question through the host. It sends the number of the option or a close action, never keystrokes, and a free-text answer is limited to 2000 characters. Each question can be answered once and expires after 5 minutes, and one device can send 10 answers a minute. For a permission prompt only a one-time yes and a no are accepted; choices such as always allow are refused. The answer is refused when the device is view only or another device holds typing. The Mac shows a short notice, Answered from and the device name, for a few seconds and does not keep the answer.

Drag files or folders from Finder and drop them on a pane. On a local pane, the paths are typed at the prompt, quoted for the pane's shell, and with broadcast on they go to every pane in the group. On an SSH pane those paths would name nothing on the server, so MXterm Pro uploads the files over SFTP and types the paths on the server instead.

• The folder is the one the terminal is in, when the server's shell reports it. If it does not, it is the folder the tab's file panel shows, and after that your home folder on the server. A drop never uploads into / unless the terminal itself is in /.
• Nothing is overwritten. A name that already exists in the folder is uploaded as name (1).ext, then name (2).ext, and the path typed is the real one.
• When the last upload has finished, the server paths of the files that uploaded are typed at the prompt with a space after them, without pressing Enter. Only that pane receives them, even with broadcast on.
• A name that contains a single quote, a backslash, ! or a control character is uploaded but not typed, because it cannot be typed safely into a shell MXterm Pro does not know.
• Only one drop runs at a time for each saved host. A second drop on a pane of the same host is refused until the first finishes.

While a drop runs, the pane shows a bar at its bottom edge: it checks the folder, then says how many items it is uploading and to which folder. When it ends, the bar says how many items were uploaded and to which folder, lists the names that were not typed, and gives each failure with its reason. A clean result disappears after 6 seconds. Failures and refusals stay until you click ✕.

Nothing is uploaded, and the bar says why, when the folder cannot be read, when the only folder known is /, or when the pane's host is no longer in SSH Manager. If the pane's SSH session is not running, the files are uploaded but their paths are not typed. A file panel that shows the folder lists the new files by itself.

You can open the panes of another MXterm Pro, on another Mac or computer, as tabs in your own window. The other MXterm is the host. Nothing is shared until the host turns it on: its server has to be running, your MXterm has to be paired with it, and the panes are shared one by one or all at once.

On the host:

1. Open Settings → Remote Access & Devices and click Start Server. The panel shows the address to use and a 6-character pairing code that expires after 5 minutes. To have the server start whenever MXterm opens, turn on Start the host server when MXterm opens in the same panel. It is off by default. A device signed in to the same MXterm account can ask to pair without the code: you tap Allow on this Mac. See Settings.
2. In the header of each pane you want to show, click the share button (the globe). Panes are not shared by default. In its menu, pick what the other device may do, view and type or only view (view and type is selected at first), then click how long to share: 30 minutes, 1 hour, 8 hours, or Share until I stop it.

To share every pane of a tab at once, right-click the tab and choose Share entire tab, pick view and type or view only, then a time. Stop sharing this tab ends those shares. A tab with shared panes shows a globe and how many of its panes are shared; when the whole tab is shared, the globe sits in a filled pill. Panes that only show another Mac's panes are skipped. To share every pane of the main window instead, turn on Share all panes in the title-bar globe: one switch, with a View or Control choice and a time that it remembers. See Settings.

While a pane is shared, its share button shows the time left if you set a deadline, and how many devices are attached when there are any. A pane shared as view only shows an eye instead of the globe. Hover the button for a summary: the mode, the time left and the number of devices attached.

The menu of a shared pane has Switch to view only or Allow typing (control), which keeps the deadline. Below it, a list of times counted from now sets a new deadline. Then come the devices attached now, each with Disconnect and a tag on the one that is typing, and Stop sharing. A disconnected device stays out of that pane until the share ends, and its pairing is kept.

A share ends when its time runs out or when you choose Stop sharing. Every device that is watching is then disconnected and whoever was typing is released. Switching to view only takes typing away from the device that had it. MXterm Pro is built to restore your shared panes after a restart once each pane is running again, and to drop any share it cannot verify.

On the Free plan you can share up to 5 panes at once by default. Sharing one more opens the upgrade prompt, which reads Free shares up to 5 panes at once for remote control. Stop sharing one, or upgrade. Changing how a pane is shared and stopping a share are not limited, and nothing already shared is stopped. mxterm.net can change this number, like the other Free limits. Pro has no limit. See Pricing.

On the Free plan, 1 other computer can control this one by default. The MXterm phone app (iPhone, iPad) is not counted toward this limit. Only other computers running MXterm count; browsers do not. Pairing one more computer opens the upgrade prompt, which reads Free lets 1 other computer control this one. Phones and tablets are not limited. Computers already paired are kept. mxterm.net can change this number too.

On your machine:

1. In the Machines section of the left sidebar, below the Terminals list, click + (Add by URL/hostname).
2. Enter the host's address as the host's panel shows it (Copy address), such as http://100.64.1.5:6868, and the pairing code, then click Add. The name is optional: left empty, the row takes the name the machine gives itself. When Tailscale finds machines, a button beside the address lists them so you can pick one instead of typing.
3. Click the machine's row to list its tabs and panes under it, then click a pane to open it: only that pane's tab opens. Open all shared panes in the row's ⋯ menu opens every shared pane at once.

Each pairing form (adding a host, editing one to connect again, and Pair again) has a Code and a Password switch: choose Password to pair with the host's access password instead of a code. It has to be turned on at the host first. A password is accepted over Tailscale, and over the local network when the host allows it, where it travels as plain HTTP. Tailscale is the encrypted choice, so prefer the host's Tailscale address (100.x.y.z) while Tailscale is running on this machine.

A pairing survives a restart of the host, which stores only a hash of each paired MXterm's token. A paired MXterm that has not connected for 30 days is dropped by the host and has to pair again. Each paired device also has Hide all panes at the host: while it is on, that device sees no panes from the host and cannot open or type into any.

The header of the Machines section has three buttons: Scan for machines, which looks for machines on your Tailscale network and lists them under a Found nearby heading (click one to start the add form with its address), Add by URL/hostname (+), and a sliders button that opens Settings → Remote Access & Devices. The section's title opens and closes it, and opening it closes the SSH list (closing the SSH list opens Machines again). Machines starts open only when a machine is paired. You can drag the right edge of the left sidebar to make it wider or narrower, between 200 and 480 pixels and at most 40% of the window. The sidebar always starts at its default width: a width you dragged is not kept once you close the sidebar or restart. The sections' heights work the other way: drag the line between Workspaces, Terminals and Machines to resize them, double-click it to reset it, and the heights are kept.

On the Free plan you can save 1 machine by default (the upgrade prompt calls it a saved Machine). Clicking + for a second one opens the upgrade prompt instead of the form. The app itself refuses a second one, not only the form. Editing, pairing again and removing are not limited, so machines you already have are kept. mxterm.net can change this number, like the other Free limits. See Pricing.

Each row shows the machine's name on the whole first line and, under it, how it is reached (such as Tailscale) and its state: how many panes it shares and how many are running (2 panes · 1 running), Offline, Never checked, or Auth failed — re-pair, which adds a Pair again button. Hover the row to see its address and the MXterm version it runs, such as v1.1.31. Machines with a running pane come first, then the most recently used, and offline ones last. MXterm checks a new machine once on its own. After that it dials again only a machine that was offline: every 30 seconds, and at once when the network comes back or the window regains focus. A machine that rejected its pairing is not retried: use Pair again. Reconnect in the row's ⋯ menu checks it right now. That menu also has Open all shared panes, Edit name and address, Pair again, Copy address and Forget machine. Open a machine and its tabs are cards with their panes under them; each pane shows one of five states, you can pin a tab, and a pane the machine does not share is drawn locked and not counted. A tab whose Control Room is live (two or more members and at least one message) has a row you can open to read its last 100 messages, read only.

You can also start things on a machine from here, without going to that computer. In the row's ⋯ menu, New Control Room… makes a Control Room from that machine's panes, and New session… opens a new session on it. Hover one of its tabs for New Control Room from this tab (shown for a tab that has no room and has panes shared with control) and New session in this tab, which starts the session in that tab. Under the tabs, a Control Rooms section with a + lists the rooms no tab card shows, such as a new room with no message yet. These entries show only for a machine that is online and supports them.

New Control Room… asks for a room name and for 1 to N of that machine's sessions that are shared with control, where N is the number of members per room its plan allows (at most 12). The dialog shows the plan's numbers, such as Rooms 1/1 · sessions per room 2, and keeps Create room off when the machine is at its plan's limit of rooms with sessions. Opening a room of that machine also shows a Members tab next to the discussion: the crown sets or clears the coordinator, each member has a remove button that asks once more, Add sessions adds sessions of that machine that are not in the room (one that is in another room moves), and Delete room asks once more. A tab's main room has no delete: delete it on that computer. The limits are those of the machine you are controlling, not of this one.

New session… has the same fields as the phone app: Run on, Project folder on that computer (pick one of that machine's tabs, or type the full folder path as that computer writes it), Agent (the agents that computer reports as installed, and a shell), Separate worktree, Skip confirmations (bypass), First task for the agent… (optional) and Start. The bypass switch shows only for an agent on a machine that allows it. Once the session has started, its pane opens here like any other pane of that machine.

The machine you control has the last word. On that computer, open Settings → Remote Access & Devices, find this computer under Authorized Remote Devices and turn on Can manage Control Rooms to make and change rooms, or Can create new sessions to start sessions. Both are off for a newly paired computer. A session with bypass also needs Allow remote bypass to be on there. When a switch is off, the dialog names the one to turn on. See Settings.

A ⚠ after the status means something is worth checking, and hovering the status shows what. It appears on an OK host whose MXterm is too old to send a pane's screen: update MXterm on that Mac. It also appears on an offline host with a Tailscale address (100.x.y.z or *.ts.net). If this Mac is not on Tailscale, sign in to Tailscale here with the same account as the other Mac. If it is, check on the other Mac that its host server is running and its Tailscale is connected under the same account. The same advice is added to the error when adding a Tailscale host fails because it cannot be reached, and to the notice when a click gets no answer.

A machine can often be reached over more than one route, such as the local network and Tailscale. When its saved address stops answering, MXterm tries the machine's other known addresses on its own, and the row's tag shows the route in use (LAN or Tailscale), with a tooltip saying the saved address did not answer. The row moves to the other address only after the saved one has failed twice in a row. Your pairing key is sent to another address only after that address has proved, without the key, that it is the machine you paired. A machine is tried on other routes once this Mac has recognised it, which happens when you pair it or at its first successful connection; until then it is reached at its saved address only. If none answers, the row reads Offline · other routes tried, and a pane says that its other routes were tried too.

Forget machine in the row's ⋯ menu asks once more before it removes anything. A small box next to the button says Remove followed by the machine's name and a question mark, and that the computer itself is not touched and you would pair it again to come back. Remove confirms; Cancel, Esc or a click elsewhere keeps the row.

To rename a host, or to point it at a new address after its address changed, open the ⋯ menu on its row, choose Edit name and address, change the name or the address and click Save. Use machine name puts back the name the machine gives itself. The host keeps its pairing, so you do not enter a code again. To connect again without deleting the row, also fill in New pairing code (only to connect again): the host is paired at that address and its key is replaced under the same row and name, and a wrong code changes nothing. The address must be an http:// or https:// origin with no path. A changed address resets the row, and MXterm checks the new address straight away.

Open all shared panes copies the machine's tab layout into your window at that moment; clicking one pane in the row's list opens only that pane's tab, built the same way, and leaves the machine's other tabs alone. Each tab that has at least one shared pane opens as a tab of your own, named <tab> — <machine>, with its panes in the same arrangement. A pane the host has not shared appears as a tile with its name and Not shared — turn on remote sharing for this pane on the host Mac. If the host shares nothing, you get a single pane in a tab named MXterm: <host> that says nothing is shared there yet and tells you to share a pane on the host and then reload. Which panes are shared, and whether each lets you type, are read at that moment too.

Open the same machine again and a tab that is already open is not opened twice. If the host changed it (a pane added, removed, shared or unshared, or a new deadline), the tab is updated in place and keeps the connections of the panes that did not change. A tab the host closed is closed here, and only tabs not open yet are added. When nothing changed, the open tab comes to the front. To pick up a later change on the host, use Open all shared panes again.

Opening a machine never fails silently. If it cannot connect, a notice appears under the row, with a ✕ to dismiss it. The notice is one of these, or just Could not reach the host. when the cause is not known:

• The machine answered, but MXterm is not running its host server there. Open MXterm on that machine and start the server, or turn on Start the host server when MXterm opens.
• There is no answer from that address: the machine may be off or asleep, or not reachable from this network.
• The address does not work because the name does not resolve. Fix it with Edit name and address in the row's ⋯ menu.
• Something answers at that address, but not as an MXterm host. Check the port, and that MXterm on both machines is up to date.
• The host no longer accepts this machine, because it was revoked there or its pairing was reset. The notice asks for the host's access password or a new pairing code in the row itself, and the click carries on once you are paired again.
• The host is no longer saved here, for example because it was removed in another window. Add it again.

A pane shows the host pane's screen as soon as it connects, because a new attach asks the host for the pane's current screen. If nothing arrives within 3 seconds, the pane asks again the older way, by replaying the host's recent output, and says so in the pane. If the pane is idle and there is nothing to show, it says [Connected — waiting for output]. If the pane stays blank, it says why: for a host that is too old to send screens it names that MXterm version and tells you to update it, and after about 4 seconds of nothing it prints how many frames the host sent, which tells a fault on the host or the network from one in your app.

The pane draws the screen at the host pane's own columns and rows, and your window does not resize the host's pane unless you ask it to with Fit to my window (see below). The text size follows your pane so the screen fills it, and a tall screen scrolls inside the pane instead of shrinking the text below a readable size. In the pane's menu, Smaller text and Larger text set a size by hand for that pane, and Auto-fit turns automatic fitting back on. Maximizing the pane, or bringing it to the middle, also turns it back on.

When the host shared the pane with control, your keystrokes go to it as soon as it connects, and the badge in its header reads In Control. Click the badge to switch to view-only; it then reads Take control, and clicking it again resumes typing. In a narrow pane the badges shrink to icons; hover one for its label. Shift+Enter and Alt+Enter type a new line in the host pane instead of sending, and text typed through an input method, such as Vietnamese Telex or VNI, reaches the host as the finished text.

If the host shared the pane as view only, the badge reads Read-only pane and typing stays off. The mode is read when the tab opens. If the host shared the pane for a limited time, the header shows the time left, and when it runs out the pane turns into an unshared tile. When you scroll up in the pane, a round arrow button at its bottom right jumps to the newest output.

A remote pane has its own header buttons: Show as chat or Show terminal, Smaller text and Larger text, Reload session (reconnects and asks the host for its screen again), Fit to my window, a maximize button, the Pane actions menu (the ⋯ button) and Close Pane. The chat button is always on a remote pane, whether or not Chat view is on in Settings. As the pane narrows, the text-size and fit buttons move into the menu below about 480 pixels and Reload session below about 380. The menu has the rest, in this order:

• Take control, only while another device holds the keyboard of this pane.
• Send Ctrl+C and Send Esc, which send that key to the host pane. They work only while you are in control.
• One row for text size: smaller, the current size, larger, and Auto-fit.
• Scroll to latest, Copy screen text (copies everything on the pane's screen), Reload session (reconnects) and Fit to my window.
• Center (double-click the header does the same) and Maximize pane. Restore pane replaces the first item while the pane is in the middle, and both items while it is maximized.

You can drag a remote pane by its header to rearrange it like any other pane of the tab, and double-click the header to bring it to the middle.

Only one device can type in a pane at a time. If another device is typing, the host refuses your keystroke: the badge reads Typing refused and typing stays off. Click the badge to take control from the other device; the host still refuses if the pane is no longer shared. The device you displaced sees Control taken, stops typing and does not reconnect by itself. Control changes hands only when a person clicks a badge; nothing takes it back automatically. The host's own web page behaves the same way: a browser that was displaced shows a notice and a Take control button, and does not reclaim control by itself.

A device the host disconnects from a pane is told so, does not reconnect by itself, and can attach again only after the host shares the pane again. Then use Reload session.

Typing in a pane belongs to one device at a time, the one that holds its writer slot. A device that is only watching does not take the slot from the one that has it. The slot is released when its device disconnects, and after 5 minutes without any activity from it in that pane.

Fit to my window asks the host to resize its terminal to the size of your pane, counted at your pane's own text size, so a bigger window gets more columns instead of bigger letters. It is in the pane's header, or in its ⋯ menu when the pane is narrow. It works only while you hold the writer slot, once the pane is connected, and when the host's MXterm is new enough to announce the resize to the person at that Mac; otherwise the button is off and its tooltip says why. If the host does not answer within 2.5 seconds, or answers with another size, the request counts as refused. The host Mac shows a notice such as A remote device resized this terminal to 120×40 with a Restore button. The terminal returns to the host's own size when the person at the host clicks Restore, when the host resizes that pane itself, when the device that asked disconnects, when typing passes to another device or is released, or when the pane stops being shared or drops to view only. Back to host size, in the same place, gives it back by hand.

When MXterm on the host restarts, for example to install an update, the pane says the host is restarting and keeps trying for about 90 seconds. Each time it asks the host for its list of panes: no answer means the host is not up yet, and it tries again. If the pane is no longer in that list, it stops at once and says the pane is gone. When the time runs out, the connection counts as failed. If the person quit MXterm on the host, the pane reads Host quit and does not retry. A host on an older MXterm gives no reason, and its pane treats the drop as an ordinary lost connection.