Skip to content

The "path" argument must be of type string #180

Description

@rccarlson

Describe the bug

Copilot seems unable to run any commands. It just returns The "path" argument must be of type string. Received undefined every time.

 ╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
 │ > set up unsloth on this computer                                                                                                                                                 │
 ╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

 ● I'll help you set up Unsloth on this computer. Let me first explore the current
   directory to understand what we're working with.

 ✗ Read /c:/Users/carlril/source/repos/unsloth
   Path does not exist

 ✗ Check current directory
   $ pwd
   The "path" argument must be of type string. Received undefined

 ✗ Check current directory
   $ Get-Location
   The "path" argument must be of type string. Received undefined

 ● Let me try a different approach:

 ✗ Check current directory and list files
   $ pwd; ls
   The "path" argument must be of type string. Received undefined

 ● Operation cancelled by user

Affected version

0.0.332 Commit: ace227c

Steps to reproduce the behavior

All commands result in this error.

Expected behavior

No response

Additional context

No response

Activity

  1. added theissue type on Oct 2, 2025
  2. rccarlson commented on Oct 2, 2025

    @rccarlson
    Author

    This is using claude-sonnet-4.5

  3. thekeenant commented on Oct 4, 2025

    @thekeenant

    Updating from Node 18.19.1 to Node 24.9.0 fixed the issue for me.

  4. williammartin commented on Oct 15, 2025

    @williammartin

    @rccarlson, can you check if a node update (minimum supported is v22) resolves this for you?

  5. thekeenant commented on Oct 17, 2025

    @thekeenant

    I'm surprised I'm able to run Copilot CLI on an outdated version of Node. Can a better error message be shown if that is indeed the culprit?

  6. williammartin commented on Oct 17, 2025

    @williammartin

    Created #341 to discuss that, thanks.

  7. EvanBoyle commented on Nov 6, 2025

    @EvanBoyle
    Collaborator

    We're now enforcing a node version check. So closing this issue out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions