This repository was archived by the owner on Jan 23, 2026. It is now read-only.
Fix PowerShell installation error with global drive#246
Merged
Conversation
Co-Authored-By: jhaynie@agentuity.com <jhaynie@gmail.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
jhaynie
approved these changes
Apr 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix PowerShell Installation Error with Global Drive
Issue
Windows users were encountering an error during installation of the Agentuity CLI:
This error occurred at line 308 in the
install.ps1script when trying to useSet-Itemwith a path that included the "global:" scope prefix.Fix
Modified the PowerShell function creation to use the proper
Function:drive instead of the "global:" scope prefix. This is the correct way to create functions in PowerShell and avoids the drive error.Changes
$tempFunctionName = "global:$exeName"Set-Item -Path $tempFunctionName -Value $scriptBlock -ForcetoSet-Item -Path "Function:\$exeName" -Value $scriptBlock -ForceTesting
This change should fix the Windows installation error without affecting any other functionality.
Link to Devin run
https://app.devin.ai/sessions/e5ef2f0da8ae41e8b2b4a0544dccd16e
Requested by: jhaynie@agentuity.com