-
Notifications
You must be signed in to change notification settings - Fork 56
Add profile integration option to AI Shell install script for persistent auto-start #389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: StevenBucher98 <[email protected]>
Co-authored-by: StevenBucher98 <[email protected]>
Co-authored-by: StevenBucher98 <[email protected]>
@Copilot please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
This PR adds the ability to configure AI Shell to automatically start when PowerShell is launched in Windows Terminal by integrating with the user's PowerShell profile.
New Features
Interactive Installation
The install script now prompts users during installation:
Non-Interactive Installation
New parameters for automation scenarios:
-AddToProfile
: Automatically add AI Shell to profile without prompting-DefaultAgent <name>
: Specify the default agent to use (e.g., "openai", "ollama", "azure")Safe Profile Management
Usage Examples
Technical Implementation
$env:WT_SESSION
is presentGenerated Profile Code
The script adds code like this to the user's profile:
Fixes #388.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
1p7vsblobprodcus324.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)1s1vsblobprodcus386.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)7tjvsblobprodcus341.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)c78vsblobprodcus322.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)d0svsblobprodcus381.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)/home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js
(dns block)fdpvsblobprodcus345.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)h6tvsblobprodcus346.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)jd4vsblobprodcus366.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)l49vsblobprodcus358.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)m16vsblobprodcus374.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)uy6vsblobprodcus34.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)vb4vsblobprodcus33.vsblob.vsassets.io
dotnet build shell/shell.sln -c Release
(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.