codespaceStatusTool.js not found

[lucasvazq]

Select Topic Area

Bug

Body

Hello 👋

I'm having trouble with my Codespaces.
Its happening recently, when i start it I got the following alert:

The terminal process "/bin/sh '-c', '$(ls ~/.vscode-remote/bin/*/node | head -n 1) /workspaces/.codespaces/shared/codespaceStatusTool.js'" terminated with exit code: 1.

So, I do:

cat /workspaces/.codespaces/shared/codespaceStatusTool.js

And I got:

cat: /workspaces/.codespaces/shared/codespaceStatusTool.js: No such file or directory

I also notice that I don't get any extension installed, and my postStartCommand doesn't execute.

This is my current devcontainer.json:

{
  "name": "xxx",
  "postStartCommand": "/bin/bash /workspaces/xxx/.devcontainer/configure.sh",
  "features": {
    "ghcr.io/devcontainers/features/docker-in-docker:2": {},
    "ghcr.io/devcontainers/features/aws-cli:1": {}
  },
  "forwardPorts": [3000, 5000, 8000],
  "portsAttributes": {
    "3000": {
      "visibility": "public"
    },
    "5000": {
      "visibility": "public"
    },
    "8000": {
      "visibility": "public"
    }
  },
  "customizations": {
    /*
      These configs are intended to:
      - Improve performance.
      - Simplify the editor.
      - Make the editor suitable for project development.

      If u see any warnings here, don't worry, we try to have some
      configurations in order to backwards compatibility.
      Also, some configs only make sense when the project is
      running in a container.
    */
    "vscode": {
      "settings": {
        // File Watching, Explorer, and Search tool.
        "files.watcherExclude": {
          "**/.git/**": true,
          "**/.pytest_cache/**": true,
          "**/__pycache__/**": true,
          "**/collected_static/**": true,
          "**/htmlcov/**": true,
          "**/media/**": true,
          "**/migrations/**": true,
          "**/patches/**": true,
          "**/staticfiles/**": true,
          "**/static/vendor/**": true,
          "**/*.pyc": true,
          "**/*.map": true,
          "**/*.min.*": true,
          "**/*.mo": true,
          "**/*.po": true,
          "**/__init__.py": true
        },
        "files.exclude": {
          "**/.git/**": true,
          "**/.pytest_cache/**": true,
          "**/__pycache__/**": true,
          "**/collected_static/**": true,
          "**/htmlcov/**": true,
          "**/media/**": true,
          "**/migrations/**": true,
          "**/patches/**": true,
          "**/staticfiles/**": true,
          "**/static/vendor/**": true,
          "**/*.pyc": true,
          "**/*.map": true,
          "**/*.min.*": true,
          "**/*.mo": true,
          "**/*.po": true,
          "**/__init__.py": true
        },
        "search.exclude": {
          "**/.git/**": true,
          "**/.pytest_cache/**": true,
          "**/__pycache__/**": true,
          "**/collected_static/**": true,
          "**/htmlcov/**": true,
          "**/media/**": true,
          "**/migrations/**": true,
          "**/patches/**": true,
          "**/staticfiles/**": true,
          "**/static/vendor/**": true,
          "**/*.pyc": true,
          "**/*.map": true,
          "**/*.min.*": true,
          "**/*.mo": true,
          "**/*.po": true,
          "**/__init__.py": true
        },
        "search.followSymlinks": false,
        "search.quickOpen.includeSymbols": false,
        "search.searchOnType": false,
        "search.useGlobalIgnoreFiles": true,
        "search.useIgnoreFiles": true,

        // Python, Pylance, and Pylint.
        "python.analysis.exclude": [
          "**/__init__.py",
          "**/migrations/**"
        ],
        "python.analysis.autoImportCompletions": false,
        "python.analysis.diagnosticMode": "openFilesOnly",
        "python.analysis.indexing": false,
        "python.analysis.typeCheckingMode": "basic",
        "python.defaultInterpreterPath": "/usr/local/python/current/bin/python",
        "python.languageServer": "Pylance",
        "pylint.args": [
          "--rcfile=.pylintrc"
        ],
        "pylint.ignorePatterns": [
          "**/__init__.py",
          "**/migrations/**"
        ],
        "pylint.importStrategy": "fromEnvironment",

        // Copilot.
        "github.copilot.chat.codeGeneration.instructions": [
          {
            "file": ".github/copilot-instructions.md"
          }
        ],

        // Telemetry.
        "docker.lsp.telemetry": "off",
        "telemetry.feedback.enabled": false,
        "telemetry.enableCrashReporter": false,
        "telemetry.enableTelemetry": false,
        "telemetry.telemetryLevel": "off",

        // Miscellaneous
        "editor.accessibilitySupport": "off",
        "editor.bracketPairColorization.enabled": false,
        "editor.guides.indentation": false,
        "editor.largeFileOptimizations": true,
        "editor.lightbulb.enabled": "off",
        "editor.minimap.enabled": false,
        "editor.renderWhitespace": "none",
        "editor.scrollBeyondLastLine": false,
        "explorer.autoReveal": false,
        "explorer.excludeGitIgnore": true,
        "extensions.ignoreRecommendations": true,
        "markdownPreviewAtStartup.markdownFilePath": "xxx/README.md",
        "scm.diffDecorations": "none",
        "terminal.integrated.enableMultiLinePasteWarning": "never",
        "workbench.editor.closeOnFileDelete": true,
        "workbench.startupEditor": "none",
        "workbench.tree.renderIndentGuides": "none"
      },
      "extensions": [
        "editorconfig.editorconfig",
        "github.copilot",
        "github.copilot-chat",
        "lucasvazquez.markdown-preview-at-startup",
        "ms-python.python",
        "ms-python.vscode-pylance",
        "ms-vsliveshare.vsliveshare",
        "visualstudioexptteam.vscodeintellicode"
      ]
    }
  }
}

I tried to create two different Codespaces and make a rebuild (full), and I keep having this issue.

If u need any extra information, let me know!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[danpolanco]

I'm also experiencing issues with a dev container setup in GitHub Codespaces where:

1. Terminal Error: The terminal process terminates with exit code 1 (see picture)
2. Extension Installation Failure: VS Code extensions fail to install properly

Error Details

Error message:

The terminal process "/bin/sh '-c', '$(ls ~/.vscode-remote/bin/*/node | head -n 1) /workspaces/.codespaces/shared/codespaceStatusTool.js'" terminated with exit code: 1.

Environment

• Platform: GitHub Codespaces
• Base Image: mcr.microsoft.com/devcontainers/base:noble (Ubuntu 24.04 LTS)
• Features: Miniforge (Conda)
• Project Type: Python bioinformatics project

Dev Container Configuration

.devcontainer/devcontainer.json

{
    "name": "demo-summary-results",
    "image": "mcr.microsoft.com/devcontainers/base:noble",
    "features": {
        "ghcr.io/rocker-org/devcontainer-features/miniforge:2": {}
    },
    "postCreateCommand": ".devcontainer/postCreateCommand.sh",
    "customizations": {
        "extensions": [
            "yzhang.markdown-all-in-one"
        ],
        "vscode": {
            "python.defaultInterpreterPath": "/opt/conda/bin/python"
        }
    }
}

.devcontainer/postCreateCommand.sh

#! /bin/bash
set -e

echo "Running post create command."

# Conda environment setup
echo "Checking Conda environment setup..."

if [ -f "environment.yaml" ]; then
  echo "Found environment.yaml. Updating Conda environment..."
  if conda init --all && conda env update -n base -f environment.yaml; then
    echo "Conda environment updated successfully."
  else
    echo "Warning: Failed to update Conda environment."
    echo "Check environment.yaml for errors or run manually."
  fi
else
  echo "Warning: environment.yaml not found. Skipping setup."
fi

# Final message
echo "Setup completed successfully."
echo "Welcome to your workstation!"

environment.yaml

name: demo_summary_results
channels:
  - conda-forge
dependencies:
  - python=3.11.*
  - pip:
      - numpy
      - pandas
      - biopython

Expected Behavior

1. Dev container should build successfully
2. Conda environment should be created and configured
3. VS Code extensions should install automatically
4. Terminal should function normally without errors

Actual Behavior

1. Terminal process fails with exit code 1
2. Extensions fail to install
3. Development environment is not properly initialized

[cmuto09]

Thanks for the report @lucasvazq and @danpolanco! We are investigating the issue.

In the meantime as a workaround you should be able to manually run your postStartCommand when you successfully connect to the Codespace, and I will update here as we have updates.

[heidiLinguist]

Also broken here. Interfering with startup for all our codespaces.

[johndunderhill]

Also broken in our system, blocking developers. postAttachCommand does not run.

[eimhin-rover]

We are also seeing this issue occur on our codespaces which is disrupting developers. Any updates on what the cause is?

[jrul222]

We are also running into the "The terminal process "/bin/sh '-c', '$(ls ~/.vscode-remote/bin/*/node | head -n 1) /workspaces/.codespaces/shared/codespaceStatusTool.js'" failed to launch (exit code: 1)." for the past few days.

However, I am not seeing the issue where postCreateCommand, postStartCommand, or postAttachCommand are not executed. The only thing I have noticed not happening is the terminal window opening that shows that postCreateCommand is running. I have got in the habit of always clicking the "Building codespace" link on initial launch so I can watch the full build, which I think should just default to open in terminal anyway as having the creation log running by default would be way more clear as to what is happening during the build. I can see how developers might be confused though because if you don't click that link or view the creation log the codespace looks like it is ready for work but in the background it is still going through the build process.

[johndunderhill]

@jrul222 Can you confirm that your postAttachCommand is being executed? Our postAttachCommand script doesn't do much, but it does produce output, and we're not seeing that, as we normally would. This command is not running for us. We verified that the script isn't starting by adding code to create a timestamp file at the start and end of the script. Neither is being created.

[jrul222]

@johndunderhill Yes, I can confirm my postAttachCommand script is being executed automatically on a fresh build. I have all of my scripts set to output the entire output into a scripts/logs directory and I am seeing those logs populated without running any additional terminal commands. I will say I have not checked to see if they fire on a rebuild. I don't often keep codespaces for long periods of time but I will let my current one time out and report back tomorrow.

[jrul222]

@johndunderhill I added the same date >/workspaces/.last-setup-vscode-started from your latest reply to the top of my postAttachCommand script and can verify the file is being created with the timestamp...

Initial codespace creation...

@jrul222 ➜ /workspaces $ cat /workspaces/.last-setup-vscode-started 
Tue Aug 26 22:55:52 UTC 2025

After stopping and restarting the codespace...

@jrul222 ➜ /workspaces $ cat /workspaces/.last-setup-vscode-started 
Tue Aug 26 23:05:40 UTC 2025

[stevenmilstein]

Same here. It only happens on rebuild. Not when I call the post create/start scripts in the terminal.

[johndunderhill]

In our testing, the file /workspaces/.codespaces/shared/codespaceStatusTool.js is not present in the workspace at container startup. Something calls that, hence the error. But we're unclear about the downstream implications of this failure.

We scavenged a copy of the missing file off the Internet (apparently somebody snapshotted a running container--???). This file is 302k, minified. We unpacked it and looked at it, but we're not entirely sure of the scope of what it does. When formatted, it's 18,000+ lines long.

Sticking this file in the expected location at the beginning of the postStartCommand script restores the previous behavior of showing a message about running the setup script during container launch (and eliminates the error).

Excerpt from .devcontainer/devcontainer.json file:

:
:
	"image": "ghcr.io/costvine/container:main",

	"postStartCommand": "scripts/setup-workspace",
	"postAttachCommand": "scripts/setup-vscode",
:
:

Excerpt from scripts/setup-workspace:

#!/bin/bash

if [[ ! -f "/workspaces/.codespaces/shared/codespaceStatusTool.js" ]]; then
	# echo 'await new Promise((resolve) => setTimeout(resolve, 60000));' >/workspaces/.codespaces/shared/codespaceStatusTool.js
	cp scripts/codespaceStatusTool.js /workspaces/.codespaces/shared/codespaceStatusTool.js
fi
:
: 

But still the postAttachCommand does not run. This is our problem. Even without the aforementioned file patched in, the postStartCommand script does appear to run. We know scripts/setup-vscode does not run because: (a) It produces a status screen, which worked previously, and we no longer see that; and (b) Because we added this to it:

#!/bin/bash

date >/workspaces/.last-setup-vscode-started
:
:

and the file does not get created/updated.

[dal-pii]

We were having the same problem yesterday, seems to be resolved now.

[cmuto09]

👋 Hey all, we rolled out a fix for this yesterday so you should no longer be seeing the issue. This update will fix the issue for all Codespaces (new and existing). Please let us know if you see it crop up again.

Thanks!

[lucasvazq]

@cmuto09

I have created a new Codespace.

• ✅ Alert doesn't show (main issue)
• ✅ All extensions installed
• ✅ postStartCommand executed

Should I close this discussion, or should your team do it?

[lucasvazq]

I forgot something: Thank you for the update! 😁

[jrul222]

Fix worked for me as well. Appreciate the quick fix!

[stevenmilstein]

I ran a Full Rebuild on an existing Codespace and still receive:

The terminal process "/bin/sh '-c', '$(ls ~/.vscode-remote/bin/*/node | head -n 1) /workspaces/.codespaces/shared/codespaceStatusTool.js'" failed to launch (exit code: 1).

[cmuto09]

@stevenmilstein would you mind trying to create a new codespace to see if the issue persists?

[stevenmilstein]

@cmuto09 I tried to create a new codespaces three times, and it fails on the "Preparing your codespace" screen.

Failed to start Codespace. Back to ...

[djholt]

Resolved for me (with a new codespace). Thanks!

[johndunderhill]

Working for us some far! :)