Repository navigation
Replies: 2 comments 3 replies
|
copilot is its own beast. I used Claude Code + Copilot to transform PAI into a copilot native tool. It's wonky and not everything works perfectly but I got to where I'm happy. For reference, my work has standardized on co-pilot so I'm trying to mirror my home setup at work. |
3 replies
|
PAI is built specifically for Claude Code — it relies on Claude Code's hook system, CLAUDE.md injection, and skills architecture, none of which exist in GitHub Copilot CLI. They're different products with different extension models. PAI won't work with Copilot. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Really interested in better understanding the PAI system, and I'm at the start of that journey. As a technical (mechanical) person, but not a developer, I'm learning in bits and pieces. I already had a Github Copilot subscription because I was using it within VSCode, so i'm wondering how portable the PAI installation truly is. There are some differences in folder naming structures. I actually got PAI working in Github Copilot CLI but it doesn't feel like it's working "well". I've had it enter things into TELOS but only because i explicitly asked it to and I have never seen the PAI banner that it appears is supposed to display after I read StartupGreeting.hook.ts. I think the constant references to the .claude folder structure is the main issue.
Anyone further down the road exploring something similar (using PAI with Copilot CLI)?
All reactions