skip to Main Content

The situation is, I want to share my settings of vscode.dev to others. That could include

  • extensions installed
  • tabs opened (not files, but some extension related tabs such as panels or previews)

So the person who clicked on the shared link can go to vscode.dev, but with my configurations.

3

Answers


  1. Try to use Settings Sync, its the easiest way: Settings Sync

    You could try to create a settings.json too, and share that file with others.

    Login or Signup to reply.
  2. I think the only solutions you have here is to use either GitHub Codespaces (Dev Containers) or store config in repository.

    Basically you will not have a link for preconfigured vscode.dev. The idea is to have all required configuration in devcontainer.json file committed it to repository. So whenever the repository is opened VSCode uses the file to configure environment.

    Also you can change you settings in Workspace and right click on extensions and click "add to workspace recommendations". That will create .vscode/extensions.json, .vscode/settings.json and commit .vscode folder into repository.

    TLDR: commit VSCode configuration files into repository and open repository in vscode.dev

    Login or Signup to reply.
  3. Look into Profiles, which can be enabled in your Settings (currently experimental but will be made generally available in vscode v1.75 due out very soon.

    Current setting in Stable: Workbench > Experimental > Settings Profiles: Enabled

    There is no setting for Profiles in the Insiders Build, it is just enabled by default. I assume when v1.75 Stable comes out that will also be the case.

    See v1.75 Release Notes: Profiles:

    We are happy to announce that the Profiles feature is now generally
    available in VS Code. A Profile can include extensions, settings,
    keyboard shortcuts, UI state, tasks, and user snippets. You can
    customize VS Code for different development scenarios like data
    science, documentation writing or for multiple programming languages
    like Python or Java. If you have different VS Code setups based on
    workflow like Work or Demo, you could also save those as different
    profiles. You can open multiple workspaces (folders) with different
    profiles applied simultaneously.

    {image omitted]

    You can also export and import profiles to share them with your
    colleagues, friends or students to help them get started with VS Code.

    The following video demonstrates how to export a profile using a
    GitHub gist in order to share it with someone. Users that receive the
    profile link can preview the shared profile in VS Code for the Web and
    import it to their local VS Code instance.

    There is a nice mp4 demonstration in the link, but it appears SO would take that format.

    You can export a Profile to a Github Gist so that it can be imported by someone else or to a local file you can share (or yourself to a new maching, etc.) – my demo shows all the settings, UI State and extensions it can include.

    More info on Profiles at v1.69 Release Notes: Settings Profiles

    demo of Profile creation and sharing

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search