how to share a devcontainer.json features list across a monorepo in 2026

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: in-product help, community forums (r/productivity, r/Notion, r/slack, r/figma, r/asana, r/googleworkspace, r/microsoft365), vendor status pages and changelogs, vendor help centers

When how to share a devcontainer.json features list across a monorepo in 2026 bites you on Visual Studio Code, Microsoft May 2026 (v1.115+), the first instinct is to restart the whole app or close every tab. Most of the time you do not have to. The steps below are what a Visual Studio Code, Microsoft May 2026 (v1.115+) power-user would do at their desk before escalating - I keep my templates folder synced for exactly these moments so the working state is recoverable.

What how to share a devcontainer.json features list across a monorepo in 2026 actually involves on Visual Studio Code, Microsoft May 2026 (v1.115+)

On Visual Studio Code, Microsoft May 2026 (v1.115+) in my experience the most useful first-pass tools are code --status CLI command, Remote-SSH: Show Log, code --verbose --log trace launch flag. Each of these surfaces a different layer of the failure - keep at least the first one in your personal notes so the next time this happens you do not start cold.

For verification on Visual Studio Code, Microsoft May 2026 (v1.115+), the methods that survive contact with a real Monday-morning workload are code --list-extensions --show-versions and git config --global core.autocrlf to debug LF/CRLF diff churn. Anything less than that and you are shipping on vibes.

Authoritative sources for Visual Studio Code, Microsoft May 2026 (v1.115+) that I cross-reference before committing to a fix: docs.github.com/copilot, learn.microsoft.com/windows/dev-environment, code.visualstudio.com/docs. Marketing blog posts and Medium writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the app.

Diagnose first, fix second

Fourth: open the vendor status page for Visual Studio Code, Microsoft May 2026 (v1.115+) (status.notion.so, status.slack.com, status.workspace.google.com, status.office.com, status.figma.com, status.zoom.us, downdetector.com as a cross-check) and the vendor X/Twitter status handle for the failing window. The smoking guns are an open incident touching the exact service area you are using, a recent post-mortem covering the same symptom, or a Trust Center advisory on a partial outage. Cross-reference the timestamp of your first failed action against the incident start time - if they match within 5 minutes, stop debugging your own setup and subscribe to the incident updates. Many vendors lag the status page behind the actual incident by 10 to 30 minutes; if Twitter and Reddit are both lit up but the status page is green, trust the crowd and treat it as upstream until proven otherwise.

Seventh: run the dedicated diagnostic option for whichever subsystem the Visual Studio Code, Microsoft May 2026 (v1.115+) signal points at. Sync suspected? Force a sync from the in-product menu (Notion: Help -> Force sync, Obsidian: command palette -> Reload, Dropbox: Preferences -> Sync, OneDrive: Settings -> Sync now), then check the sync status icon for the green checkmark and the last-synced timestamp. Account suspected? Sign out fully (not switch account), clear the local credential store, sign back in with the canonical work account. Cache suspected? Clear the app cache (most apps expose this under Help -> Troubleshoot or Settings -> Advanced) and let it re-download the workspace from scratch. Each of these surfaces config that the app silently inherits from a previous session, and 90 percent of "this used to work yesterday" reports trace to a stale local state. Capture the result of each step in your notes alongside the timestamp so you do not redo the discovery the next time.

Sixth: pin down the latency and reliability envelope on the Visual Studio Code, Microsoft May 2026 (v1.115+) session under real working conditions. Run a long-duration sanity test by performing the failing action 10 times over 15 minutes, logging the timestamp and the result (success / error code / which toast appeared) per attempt to a notes file. Watch for the breakpoint where the success rate dips below 80 percent - that is your real signal that something is wrong, not the one-off failure that prompted the investigation. If you are on a marginal network (cafe wifi, mobile hotspot, hotel network), run the same test on a wired or known-good connection before assuming the app is the problem. Capture the breakpoint in your personal notes next to the app version, the account, and the workspace id - the next time this happens to a teammate, the notes are gold.

Field notes from real Visual Studio Code, Microsoft May 2026 (v1.115+) sessions

Whenever a teammate pings me about Visual Studio Code acting up, I make them open Dev Containers: Show Container Log before we even look at the symptom they reported. For Dev workflows I keep a personal log of "what bit me in Visual Studio Code and how I unstuck it", writing it down the first time saves the next afternoon. Before I mark a Visual Studio Code ticket resolved I always run `Check chrome://gpu equivalent via Developer: Toggle Developer Tools -> chrome://gpu` once more and screenshot the output, that habit has caught at least three silent regressions for me.

Tools I actually reach for

For most Visual Studio Code, Microsoft May 2026 (v1.115+) stalls I start with Developer: Show Running Extensions, fall back to code --verbose --log trace launch flag, GitHub Copilot Chat: Show Logs output channel when Developer: Show Running Extensions cannot surface the answer, and keep code --status CLI command handy for the cases where neither answers. That ordering is not academic - it matches the layers of the failure as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the failing screen is still open, not after I have already restarted the app.

Verification I run before I call it fixed

Before I mark a Visual Studio Code, Microsoft May 2026 (v1.115+) stall resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

Get-Process Code | Select-Object Id, WorkingSet64

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

node -p process.arch inside the integrated terminal

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

code --list-extensions --show-versions

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

ls ~/.vscode-server/bin to confirm correct arch directory exists

Only when every line above runs clean do I close the loop and update my notes with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Visual Studio Code, Microsoft May 2026 (v1.115+) detail, the disambiguation order I lean on is stable. I usually check code.visualstudio.com/docs for the ground-truth view on this part of Visual Studio Code, Microsoft May 2026 (v1.115+). I usually check code.visualstudio.com/updates for the ground-truth view on this part of Visual Studio Code, Microsoft May 2026 (v1.115+). I usually check containers.dev for the ground-truth view on this part of Visual Studio Code, Microsoft May 2026 (v1.115+). I usually check docs.github.com/copilot for the ground-truth view on this part of Visual Studio Code, Microsoft May 2026 (v1.115+). Marketing blog posts and Medium writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

If the Visual Studio Code, Microsoft May 2026 (v1.115+) app is slow, stale, or serving cached errors, work the cache and CDN stack in order. Sign out of the desktop app, quit it fully (Cmd+Q on macOS, right-click the system tray icon -> Quit on Windows - not just the close button), reopen, sign back in. Clear the local cache (Notion: Help -> Clear cache, Slack: Help -> Troubleshooting -> Clear cache and restart, Microsoft Teams: right-click tray icon -> Quit, then delete %AppData%/Microsoft/Teams cache folder). Hard-refresh the web app with Ctrl+Shift+R (or Cmd+Shift+R on macOS) to bypass the local browser cache. Always capture timing before the cache clear to baseline: time how long the failing action takes three times, write it down, then repeat after the cache clear so the delta is provable in your notes. Decision point: managed-device issues go through your IT admin for a tenant-wide config push; personal-device issues go through the in-product Help + Diagnostics flow before you escalate to support.

For any Visual Studio Code, Microsoft May 2026 (v1.115+) failure that smells like auth or permission, walk the principle of least surprise chain in order. Confirm which account you are actually signed into (top-right avatar on web, account menu on desktop, profile tab on mobile) and confirm it matches the email the doc was shared with. Many "I cannot open this link" reports trace to the link being shared with your personal Gmail while you are signed into your work Google Workspace identity on the same browser profile. Sign out of every account, sign back in with only the canonical work account, and retry. Clear the OAuth grant from the Visual Studio Code, Microsoft May 2026 (v1.115+) connected-apps page if you suspect a stale third-party token (Slack: Apps -> Configure, Google: account.google.com -> Security -> Third-party apps, Microsoft: myaccount.microsoft.com -> Apps and services). Decision point: if the account is correct, the doc is shared with that account, and the action still fails with a permission error, ask the doc / workspace owner to re-share explicitly and to check their workspace-level sharing policy for a new restriction.

If the Visual Studio Code, Microsoft May 2026 (v1.115+) symptom started after an app auto-update, a browser extension install, or a workspace setting change, treat versioning and environment as the prime suspect. Roll the app back to the previous build if the Visual Studio Code, Microsoft May 2026 (v1.115+) app supports it (most do not auto-rollback - in that case, sign in on the web app to bypass the desktop build entirely while you wait for a fix). Open a private / incognito browser window with no extensions, sign in, and reproduce; if private-window works, the issue is a browser extension or a cached service worker. If both desktop and private-web fail with the same payload and the same account, you have an account-level or workspace-level issue. Decision point: if the rolled-back or private-window session still fails and you are on a paid plan, open the in-product help chat with the failing screenshot; on the free tier the path is the community forum or r/visual with a minimal reproduction. Save the working app version to your notes so the next rollback is a one-line "install build X."

Automate this fix so you do not do it twice

Scrape Visual Studio Code, Microsoft May 2026 (v1.115+) workspace audit log + integration log via scheduled job

For the Visual Studio Code, Microsoft May 2026 (v1.115+), workflow faults usually surface as failed integration runs, audit-log denials, or quota nags before a full hang. A weekly scheduled job that exports the last 7 days of these events to CSV gives you a paper trail to correlate with app updates, policy changes, and vendor incidents without staring at the settings panel live. Register the task via cron (Linux / macOS), Windows Task Scheduler (schtasks /create /XML), or a GitHub Actions schedule, then write the CSV to Dropbox / OneDrive / Google Drive for retention. Subscribe a simple dashboard (Google Sheets with a daily import, Airtable scheduled sync, Notion database via the API) to the same bucket so audit events from every Visual Studio Code, Microsoft May 2026 (v1.115+) workspace converge on a single view without per-workspace clicking.

# Notion - export workspace audit log via the API (Enterprise only)
curl -X POST https://api.notion.com/v1/audit_logs \ -H "Authorization: Bearer $NOTION_TOKEN" \ -H "Notion-Version: 2022-06-28" \ -d '{"start_date":"2026-05-24","end_date":"2026-05-31"}' \ -o visual-audit-log.json
# Slack - export analytics for last 7 days via the SCIM / Audit Logs API
curl -G https://api.slack.com/audit/v1/logs \ -H "Authorization: Bearer $SLACK_AUDIT_TOKEN" \ --data-urlencode "oldest=$(date -d '7 days ago' +%s)" \ -o visual-slack-audit.json

Monitor + alert via Visual Studio Code, Microsoft May 2026 (v1.115+) admin reports, audit logs, and personal dashboard ingestion

For the Visual Studio Code, Microsoft May 2026 (v1.115+), the most useful long-running telemetry is the admin reports + audit logs shipped to a personal dashboard (Google Sheets daily import, Airtable scheduled sync, Notion database via the API, Grafana with a CSV source) and graphed on a single view. Pair that with synthetic monitoring (a small script that opens the failing page or runs the failing action every 5 minutes from at least two devices) so a regional incident lights up before teammates report it. Subscribe the personal inbox or a private Slack channel to the Visual Studio Code, Microsoft May 2026 (v1.115+) status page (Atom/RSS or Statuspage webhook) plus the vendor X/Twitter status handle so an open incident self-correlates with the synthetic failures.

# Tiny synthetic monitor - hit the Visual Studio Code, Microsoft May 2026 (v1.115+) health page every 5 minutes
while true; do curl -s -o /dev/null -w "%{http_code} %{time_total} $(date -Iseconds)\n" \ -H "Authorization: Bearer $TOKEN" \ https://api.example.com/v1/me \ >> ~/logs/visual-synth.log sleep 300
done

Codify the app version pin and rollback as a single notes entry

Once a stable app version is identified for the Visual Studio Code, Microsoft May 2026 (v1.115+), write the version string, the build hash, and the workspace policy state to a personal notes entry with the date in the title. Reproducible rollback is then a single download-and-install plus a sign-in. Pin the workspace policy state explicitly so a vendor-side default change does not silently shift behavior under you. Stage the notes entry next to a checklist that lists the failing screenshot, the Visual Studio Code, Microsoft May 2026 (v1.115+) incident id (if any), and the support case number; the second time the workflow breaks at 9 a.m. you do not want to be rediscovering which app build was actually green.

# Personal notes template (visual)
Date: 2026-05-31
App: visual
Working build: 2.45.1 (Build hash: a1b2c3d)
Account: [email protected]
Workspace: ws-prod-visual
Failing screenshot: ~/notes/visual-2026-05-31.png
Support case: SUPP-visual-12345
Rollback path: download installer from vendor releases page, sign out, reinstall, sign back in

Common pitfalls and what to watch for

Read-only validation before any write is the single step most Visual Studio Code, Microsoft May 2026 (v1.115+) fixes skip, and it is the step that lets you roll back when a fix backfires. Screenshot every existing settings page (the workspace settings, the sharing policy, the connected-apps list, the members page, the plan tier page), capture the failing screenshot in a notes entry, export the relevant log to CSV if the app supports it (Slack analytics export, Notion audit log, Google Workspace report download), and screenshot the activity feed showing the failing window before any change. On Visual Studio Code, Microsoft May 2026 (v1.115+) workspaces with multiple environments (test workspace, real workspace) record the app version, the settings state, and the connected-apps list in each before toggling anything, because a "fix" pushed only to the test workspace is a known regression vector when the real workspace has a different policy.

The mirror-image mistake is confusing a user-side symptom with a vendor fault on Visual Studio Code, Microsoft May 2026 (v1.115+). A persistent 403 is often a share-level change pushed by the doc owner rather than a Visual Studio Code, Microsoft May 2026 (v1.115+) bug. A "document not found" can be a moved page rather than a deleted one. A "webhook not firing" is frequently a corporate proxy or firewall dropping the Visual Studio Code, Microsoft May 2026 (v1.115+) egress IP rather than a vendor-side regression.

Verify the fix worked

• Reproduce the original failing action against Visual Studio Code, Microsoft May 2026 (v1.115+) on the same device AND a second device with the same account. If the failing toast or error code still surfaces on any device, you have not fixed it.
• Watch for 24 to 48 hours via the Visual Studio Code, Microsoft May 2026 (v1.115+) workspace audit log + the integration history + your personal notes. Cached error states and CDN caches mask slow-burn drift and intermittent regional issues.
• Smoke-test under realistic load: replay the workflow against a test workspace for at least 30 minutes at your normal working pace, log success / error and the timestamp per attempt to a notes file.
• Capture the new state in a personal notes entry so the next time this happens you do not rediscover it. Note app version + workspace policy + connected-apps list + failing screenshot + verbatim error string + fix applied. Push to a shared team wiki if your team uses one.
• If the fix involved an API token rotation or a workspace policy change, commit the new token to your password manager and screenshot the workspace settings for archival.

Safety, rollback, blast radius

• Test in a Visual Studio Code, Microsoft May 2026 (v1.115+) test workspace or on a duplicate page first before any change that touches the real workspace. Snapshot the app version, the workspace settings, the connected-apps list, and the sharing policy before changing anything.
• Apply the principle of least surprise when granting share access or connected-app permissions. Review the share list against the people who actually need access - extra shares are extra blast radius.
• Use idempotent imports where the Visual Studio Code, Microsoft May 2026 (v1.115+) API supports it (Notion page id de-dupe, Asana task external_id, Airtable record id) so a retried import does not create duplicate records.
• Know your rollback path. App version rollback is a one-line download-and-install; an API token rotation is reversible if you kept the old token in the password manager during cutover; a workspace policy change is reversible only if you saved the previous policy in a screenshot.
• For team-wide or workspace-wide changes, line up a maintenance window with team notification before pushing through the admin console.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to share a single Canva Brand Kit across multiple Teams without duplicating logos
• how to share a Figma library across multiple teams without duplicating components
• how to create a custom building block in Docs and share it across a Workspace domain
• how to share a named function library across a Workspace domain in Google Sheets
• how to share custom Neural Filters preset library across a creative team
• how to enable Liquid Mode for technical PDFs on Acrobat desktop 2026