Specify Panes in a Profile

Description of the new feature/enhancement

The ability to save a tab with panes as a profile, or specify in a profile the panes to open when you open that profile.

I Have 6 projects I work on, on a daily basis at work, so I come in, open up ConEmu, and it opens a tab with 6 panes each set to a different git directory. Then I begin working.

So I want to make a project profile which opens up that setup.

Currently being able to make panes is awesome, but I don't want to set it up every time I accidentally close the terminal or I reboot my computer.

(I hope this matches the requirement of the template)

I have similar needs too. Having able to define a profile with multiple panes, their layout and the profile to load in each pane would be really helpful.

This is probably the last thing stopping to switch from ConEmu.

I'd love to see this implemented. I was just looking for it in the 1.0 release, in case I missed it.

I would like for this feature to allow the user to configure multiple sub profiles within a profile. I have a test environment which composes of four hosts. I'd like to set up a profile that SSH into all of the hosts in different panes.

There are a few ways this could be achieved:

Add a concept of panes to profiles, such that panes can be specified instead of a command line, WSL profile or Azure Terminal profile. The panes then specify the profiles that they use.
- Drawback to this approach is that it overloads the concept of profiles.
- Another drawback is that it makes profiles confusing since they become self-referential.
- Panes could be specified as first, second and split direction, alternatively they could be a list and a split direction where the panes would be evenly split along that axis (but that's harder to do with the existing implementation).
- Example settings specification:

"profiles": {
    "list": [
        {
            "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
            "hidden": false,
            "name": "Project A",
            "panes": {
                "first": {
                    "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"
                },
                "second": {
                    "panes": {
                        "first": {
                            "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"
                        },
                        "second": {
                            "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"
                        },
                        "split": "vertical"
                    },
                    "split": "horizontal"
                }
            }
        }
    ]
}, ...

Add a concept of startup actions to profiles, similar to the keybinding actions, that get executed as soon as the profile is selected.
- This adds the flexibility of running other actions aside from just pane management.
- This extends/reuses the existing concept of actions, so it's easy to learn.
- Drawback to this approach is that it's a bit hacky and probably not the best choice for the long term.
- Another drawback is that setting up a layout becomes difficult and unintuitive (ex. an even four way split would require changing the focused pane after splitting twice, like the example below).
- Example settings specification:

"profiles": {
    "list": [
        {
            "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
            "hidden": false,
            "name": "Project A",
            "startupActions": [
                { "action": "splitPane", "split": "vertical", "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"},
                { "action": "splitPane", "split": "horizontal", "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"},
                { "action": "moveFocus", "direction": "left" },
                { "action": "splitPane", "split": "horizontal", "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"}

            ]
        }
    ]
}

Add a concept of "layouts". Layouts would show up beneath profiles in the menu and would be a separate element in the settings file.
- Each Layout would specify the panes that comprise it (let's call it a LayoutPane) as well as metadata (name, icon, etc.)
- Each LayoutPane would specify the profile that should be used for that pane (or specify a profile inline) similar to the existing splitPane action. By separating the concept of layouts from profiles, profiles can easily be used in this way without ambiguous or confusing cases.
- Example settings specification:

"layouts": 
    [
        {
            "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
            "hidden": false,
            "name": "Project A",
            "panes": {
                "first": {
                    "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"
                },
                "second": {
                    "panes": {
                        "first": {
                            "profile": "{2c4de342-38b7-51cf-b940-2309a097f518}"
                        },
                        "second": {
                            "commandline": "powershell.exe",
                            "startingDirectory": "%USERPROFILE%\\git\\ProjectA"
                        },
                        "split": "vertical"
                    },
                    "split": "horizontal"
                }
            }
        }
    ]
}

Ali Hosseini Khayat (@ali-hk)

That's a great writeup Ali Hosseini Khayat (@ali-hk). I think this thread needs to be better linked up to #1571, because I've been doing most of the planning for this feature in that thread unfortunately.

I think the plan of record right now is to have the user be able to specify arbitrary actions in the new tab dropdown. This will let the user set something like

"newTabMenu": [
    { 
        "type":"action", 
        "action": { "command": "wt", "commandline": "split-pane -p cmd ; split-pane -p PowerShell" }
    },
}

Which would create an entry in the new tab menu which would create two new splits, with cmd and PowerShell. In the future, this might be a bit more ergonomic (rather than using the wt commandline args), but this'll work for now.

Right now, I do something similar to create a command in the command palette that opens a bunch of tabs and splits for me:

{ 
    "command": 
    { 
        "action": "wt", 
        "commandline": "new-tab --title OpenConsole cmd.exe /k #work 15 ; split-pane --title OpenConsole cmd.exe /k #work 15 ; split-pane -H cmd.exe /k media-commandline ; new-tab --title \"Symbols Script\" powershell dev\\symbols.ps1 ; new-tab -p \"Ubuntu 18.04\" ; new-tab -p \"microsoft/Terminal\" ; sp -V -p \"microsoft/Terminal\" ; sp -H -p \"microsoft/Terminal\" ; focus-tab -t 0" 
    },
    "name": "Good Morning" 
},

This is just about the only thing keeping me from switching away from Cmder/ConEmu. Personally, I'd just like a "Save as profile" option.

FWIW, you can do something similar today with the Command Palette and the multipleActions action. It won't be able to appear in the new tab dropdown till we complete this issue, but the Command Palette is arguably a better UI 😉

From the docs:

Run multiple actions

This action allows the user to bind multiple sequential actions to one command.

Command name: multipleActions

Parameters

Name	Necessity	Accepts	Description
`actions`	Required	Array of Actions	The list of `action` to run.

Example

{ "name": "Create My Layout", "command": { 
    "action": "multipleActions",
    "actions": [
        // Create a new tab with 3 panes
        { "action": "newTab", "tabTitle": "Work", "colorScheme": "One Half Dark" },
        { "action": "splitPane", "split": "vertical", "profile": "Windows PowerShell", "tabTitle": "Work", "colorScheme": "Campbell Powershell", },
        { "action": "splitPane", "split": "horizontal", "profile": "Windows PowerShell", "tabTitle": "Work", "colorScheme": "Campbell Powershell", },

        // Create a second tab
        { "action": "newTab", "tabTitle": "Misc"},

        // Go back to the first tab and zoom the first pane
        { "action": "prevTab", "tabSwitcherMode": "disabled" },
        { "action": "moveFocus", "direction": "first"},
        "togglePaneZoom"
        ]
}}

Does "It won't be able to appear in the new tab dropdown till we complete this issue" mean that adding a multipleActions to my settings.json will have no effect right now, or can I execure it even if it dpesn't appear in the new tab dropdown?

i.e. I want to create following pattern with single command/click
 +-----+-----+
 |     |     |
 +-----+-----+
 |     |     |
 +-----+-----+
So far the best command I can get is like:
wt.exe -d d:\home ; split-pane wsl.exe ~ ; move-focus left ; split-pane wsl.exe ~ ; move-focus right;  split-pane wsl.exe ~

Edit:
Update 2026-02-05

As today, with Terminal Preview v1.24.10212.0 (idk if this feature is older than that), you can change the splitMode. Then, just put as duplicate and the pane will be duplicated based on the first one. Moving the cursor back to first panel is the same as before.

{
	"command": {
		"id": "User.multipleActions.9286D3BE",
		"name": "Dev"
		"action": "multipleActions",
		"actions":
			[{
				"action": "splitPane",
				"profile": "PowerShell",
				"split": "right",
				"splitMode": "duplicate"
			},
			{
				"action": "splitPane",
				"profile": "PowerShell",
				"split": "down",
				"splitMode": "duplicate"
			},
			{
				"action": "moveFocus",
				"direction": "left"
			},
			{
				"action": "splitPane",
				"profile": "PowerShell",
				"split": "down",
				"splitMode": "duplicate"
			},
			{
				"action": "moveFocus",
				"direction": "up"
			}
		]
	},    
},

Original post:

Today, with 1.19.3172.0 I get this exactly layout with multipleActions setting, as said before:

{ 
  "name": "Development", "command": { 
    "action": "multipleActions",
      "actions": [
        { "action": "splitPane", "split": "right", "profile": "PowerShell"},
        { "action": "splitPane", "split": "down", "profile": "PowerShell"},
        { "action": "moveFocus", "direction": "left"},
        { "action": "splitPane", "split": "down", "profile": "PowerShell" },
        { "action": "moveFocus", "direction": "up"},
    ]
  }
},

To help me with command palette, I changed it to F1:

{
  "command": 
    {
      "action": "commandPalette"
    },
  "keys": "f1"
}

startupActions is not working for me with the setup, but command palette + multipleActions already helps me.

Are you nesting your actions block ("Development") within the context of the overall "actions" array? I'm still getting an "Incorrect type. Expected "object"." on the bracket in:
"action": "multipleActions",
"actions": [

{
    "$help": "https://aka.ms/terminal-documentation",
    "$schema": "https://aka.ms/terminal-profiles-schema-preview",
    
    "actions": [
        { 
            "name": "Development", "command": { 
              "action": "multipleActions",
                "actions": [
                  { "action": "splitPane", "split": "right", "profile": "PowerShell"},
                  { "action": "splitPane", "split": "down", "profile": "PowerShell"},
                  { "action": "moveFocus", "direction": "left"},
                  { "action": "splitPane", "split": "down", "profile": "PowerShell" },
                  { "action": "moveFocus", "direction": "up"}
              ]
            }
          },
        {
            "command": {
                "action": "copy",
                "singleLine": false
            },
            "keys": "ctrl+c"
        },
        {
            "command": "paste",
            "keys": "ctrl+v"
        },
        {
            "command": "find",
            "keys": "ctrl+shift+f"
        },
        {
            "command": {
                "action": "splitPane",
                "split": "auto",
                "splitMode": "duplicate"
            },
            "keys": "alt+shift+d"
        }
    ],

That's bizarre. That should absolutely work. Which version are you on? By all accounts, the json above should just work...

I agree that it's bizarre ;-)

Version 1.19.3172.0.

Oh, it's just the schema that's wrong? That's not the end of the world - the terminal should still work, even if VsCode complains. The schema has always been more of "guidelines" than actual rules.

terminal/doc/cascadia/profiles.schema.json

Lines 1490 to 1511 in a2bb313

    
           "MultipleActionsAction": { 
        
             "description": "Arguments for the multiple actions command", 
        
             "allOf": [ 
        
               { 
        
                 "$ref": "#/$defs/ShortcutAction" 
        
               }, 
        
               { 
        
                 "type": "object", 
        
                 "properties": { 
        
                   "action": { 
        
                     "type": "string", 
        
                     "const": "multipleActions" 
        
                   }, 
        
                   "actions": { 
        
                     "$ref": "#/$defs/ShortcutAction", 
        
                     "type": "array", 
        
                     "minItems": 1, 
        
                     "description": "A list of other actions." 
        
                   } 
        
                 } 
        
               } 
        
             ],

I can't say I know enough about json schema rules to understand why that doesn't work though

Gee, who'd've thought of actually trying it to see if it works? :-o

I (mistakenly) assumed that if I got squigglies in Code, there was something wrong. Needless to say, the command -- as you suggested -- works just fine.

Tried some other settings and, if I make something wrong, Terminal will warn me and does not load the config file, so seems to be an "error-free zone".

Tip: If you want to load other profiles, like a WSL on the right side and PowerShell on the left, just change the profile key to match the namekey of one of your profile on the list below (normally).

Thanks. That was the idea. I have a terminal I open to four boxes (Fedora, Arch, Ubuntu, Raspbian) for demonstrations. I was tired of splitting manually ;-)

Allow actions in the new tab dropdown (#17281)

Navigation Menu

Repository navigation

Specify Panes in a Profile #3759

Description of the new feature/enhancement

12 remaining items

Run multiple actions

Parameters

Example

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	"MultipleActionsAction": {
	"description": "Arguments for the multiple actions command",
	"allOf": [
	{
	"$ref": "#/$defs/ShortcutAction"
	},
	{
	"type": "object",
	"properties": {
	"action": {
	"type": "string",
	"const": "multipleActions"
	},
	"actions": {
	"$ref": "#/$defs/ShortcutAction",
	"type": "array",
	"minItems": 1,
	"description": "A list of other actions."
	}
	}
	}
	],

Specify Panes in a Profile #3759

Description

Description of the new feature/enhancement

Activity

shreedhark commented on Jan 16, 2020

SergioLuis commented on May 20, 2020

JasonWThompson commented on Aug 27, 2020

ali-hk commented on Sep 27, 2020

zadjii-msft commented on Oct 1, 2020

reginbald commented on Oct 22, 2020

12 remaining items

ScottBeeson commented on Jan 23, 2023

zadjii-msft commented on Jan 23, 2023

Run multiple actions

Parameters

Example

fomrat commented on May 25, 2023

AdrianoCahete commented on Jan 30, 2024

fomrat commented on Jan 30, 2024

zadjii-msft commented on Jan 30, 2024

fomrat commented on Jan 30, 2024

zadjii-msft commented on Jan 30, 2024

fomrat commented on Jan 30, 2024

AdrianoCahete commented on Jan 30, 2024

fomrat commented on Jan 30, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions