microsoft / microsoft/vscode

Applying a directory C&P feature inside the editor

Open
#331,054 0 comments 0 reactions 1 assignee Claimed by @lramos15 View on GitHub
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

Type: Feature Request

I noticed that there is a copy and paste feature through the terminal, for obtaining current directories (only the current directory). This feature could also be applied to the top of the script being edited. Ultimately, if you implemented a hierarchical tree file system inside of the "Explorer" tab that currently contains the current working directory. You could remove the the current system, and or could implement a more sophisticated hierarchical tree file system. With the current working directory with a copy and paste text window above the hierarchical tree file system. Then the user could explore their systems files contents from within the application, no need for opening windows to access the files anymore (Unless opening up a selective project). Honestly Even recreating a new tab could allow the user to keep track of their current project directory, and their entire file system. This could be a optional feature, included upon download, as this would allow for use of a singular application needed to be ran while working with Visual Studio Code. Most Developers, more then likely keep well structured directories, and know where their projects files are already at on their device. If they don't, they could save a separate file containing the directories during sessions to easily gather their files instead of locating each and every individual file. Truthfully with your built systems, you could format a typefile saved inside Visual Studios internal features that would allow the user to save this typefile internally, They would be able click the directories within this visual studio type file format that would update the hierarchical tree file system tab, they could then use and save this typefile in between sessions. Making, accessing files, and directories a little bit easier then trying to locate everything through another process.

VS Code version: Code 1.133.0 (a5b500951314efd502d07465bd138dfbd714a960, 2026-08-11T22:14:08Z)
OS version: Windows_NT x64 10.0.26200
Modes:

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz (20 x 3696)|
|GPU Status|2d_canvas: enabled
GPU0: VENDOR= 0x10de, DEVICE=0x1e84 [NVIDIA GeForce RTX 2070 SUPER], DRIVER_VENDOR=NVIDIA, DRIVER_VERSION=32.0.16.1047 *ACTIVE*
GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.8972
Machine model name:
Machine model version:
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgpu: enabled
webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.87GB (22.23GB free)|
|Process Argv|--crash-reporter-id c27fcf68-4f70-44f1-8cf5-41fb8c2f833d|
|Screen Reader|no|
|VM|0%|
Extensions (6)

Name|Identifier|Author|Version
---|---|---|---
x86 and x86_64 Assembly|13xforever.language-x86-64-assembly|13xforever|3.1.5
Code Runner|formulahendry.code-runner|formulahendry|0.12.2
CMake Tools|ms-vscode.cmake-tools|ms-vscode|1.23.52
C/C++ DevTools|ms-vscode.cpp-devtools|ms-vscode|0.5.14
C/C++|ms-vscode.cpptools|ms-vscode|1.32.2
C/C++ Extension Pack|ms-vscode.cpptools-extension-pack|ms-vscode|1.5.1

A/B Experiments

```
vsliv368cf:30146710
vswsl492:30256859
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
envsactivate1:31551504
cloudbuttont:31379625
3efgi100_wstrepl:31403338
ddidtcf:31399634
ec5jj548:31422691
cp_cls_t_966_ss:31526232
4je02754:31466945
c3h7c220:31478652
cp_cls_c_1081:31454833
conptydll_true:31498968
e9c30283:31461165
test_treatment2:31471001
c9b86496:31447327
ei9d7968:31496641
chat:31457767
ghj88844:31499326
ec1eg703:31520046
ddid_c:31478207
hmra_i5g22:31518061
7df3h592:31512476
cp_cls_t_1082:31535311
logging_enabled_new:31498466
j0d79568:31499440
jb_cp_cls_t_632:31543129
56dj4588:31512888
32d76977:31512328
ha629193:31508444
cdk-lw-on:31524445
a1ije391_t:31540920
jbcp_cls_pctr_t:31531130
61138546:31518536
cp_intellij_t_nes:31548657
d7b18187:31526828
ahp-both-windows:31556933
session_8:31532895
ihg5j128:31534457
f412h606:31551416
7g2b5551:31542111
5fe6f778:31566737
allow-none:31555437
fd5dc207:31551400
ac562147:31564510
c7c27ce7:31554789
1h923230:31564177
0dg73464:31554319
treatment-23-1:31555779
unuse_dynamic_mcp:31555281
0c1h4866:31566224
session-archive:31558132
5b8j3302:31564601

```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.