🚨 🚀 Big Improvements Coming to PAI in 3.x and Beyond #500
Replies: 10 comments 9 replies
-
|
Dang, @danielmiessler - you are moving lightning Fast man, I didn't even had the chance to integrate all 2.4 Features yet and you're preparing the 3.0 Push ;P |
Beta Was this translation helpful? Give feedback.
-
|
No, there's plenty of time. We're just planning for the future.
…On Mon, Jan 26, 2026 at 23:37, Steffen < ***@***.*** > wrote:
Dang, @danielmiessler ( https://github.com/danielmiessler ) - you are
moving lightning Fast man, I didn't even had the chance to integrate all
2.4 Features yet and you're preparing the 3.0 Push ;P
—
Reply to this email directly, view it on GitHub (
#500 (comment)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AAAMLXWDCIYUMI7I7P6WEHD4I4IVDAVCNFSM6AAAAACS7XPOV2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNRRGQZTMNQ
).
You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/500/comments/15614366
@ github. com>
|
Beta Was this translation helpful? Give feedback.
-
|
Dan - @danielmiessler, thank you so much for everything you’ve built with PAI. Seeing this discussion tagged as #500 almost feels symbolic in a way — like a gentle reminder of the “internal issues” in the current workflow that you’re now addressing so decisively in the 3.x direction. It’s a fitting number for a turning point. Due to some economic limitations, I’ve mostly relied on free or local-first tools like OpenCode, Ollama, and a Windows-based setup. There’s also the wonderful pai-opencode project from @Steffen025, which I think holds real potential for people in similar circumstances in the future. Because of my environment, I’ve run into quite a few obstacles trying to keep things stable. Eventually, I created a much more simplified version inspired by PAI. It’s missing many advanced features, but even in that minimal state, it has meaningfully improved both my personal workflow and my daily work. I mainly wanted to say this: |
Beta Was this translation helpful? Give feedback.
-
|
@phamwon ty so much for the Appreciation - it really means A LOT to me - i can absolutely relate to what you are feeling about an awakening - same same with me. Be sure tho - there are some REALLY great things coming to PAI-OpenCode - I’m coding like crazy - but this week i need to focus on a local AI Summit here in Germany this weekend that I will attend - so stay tuned 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Would love to hear about your experience running PAI on open infra as that directly relates to @danielmiessler's "it's the harness, not the model" thesis. I have a feeling I'll be engaging with it soon too. Any chance you'd want to write an article/come on a podcast to chat it thru? Onwards! |
Beta Was this translation helpful? Give feedback.
-
|
@xonack - at the moment I still run Mainly Claude models (max subscription), so my experience is "limited" / focused on the software foundation - like CC vs OC. |
Beta Was this translation helpful? Give feedback.
-
|
Off the top of my head, comparing and contrasting CC vs OC seems incredibly interesting to me because one of Daniel's courts is that the models don't matter - CC might still have a better scaffold, but for how long? |
Beta Was this translation helpful? Give feedback.
-
|
Brother just can't be stopped. |
Beta Was this translation helpful? Give feedback.
-
|
@danielmiessler - I already shot it on Discord but I wanted it to stay somewhere relevant: That really could be something quite interesting- as well as NOT SEEN BEFORE NOWHERE |
Beta Was this translation helpful? Give feedback.
-
|
Is this going to come up against the same T&Cs violations that Clawdbot users are now faced with? |
Beta Was this translation helpful? Give feedback.
-
|
Good question @DavidMooreUK No. We use literally the Claude CLI (so does @pedramamini Maestro). So we're not spoofing their OAuth flow or doing anything like capturing the OAuth token and pasting it into a third-party tool. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good! Slow and Steady for the win. |
Beta Was this translation helpful? Give feedback.
-
|
We want to be fast and steady (safe), but in the meantime, we have to slowly and deliberately set things up so we can get to that fast and safe state. 😃 |
Beta Was this translation helpful? Give feedback.
-
|
@danielmiessler & @ksylvan, 4 day user here. Just wanted to say thanks for this work. It has definitely expanded the way I think about this space. I wanted to share that I have PAI installed on Windows and installation was 9 out of 10 difficult. It was a 4-5 hour adventure. I'm quite technical and would have failed had it not been for the ability to ask Claude basic questions like "xyz isn't working, go fix.", "check this again...", etc. As you think about future versions, how are you thinking about Windows (WSL) support? (this isn't a feature request, just a Window's user chiming in so you know we're out here :-) ) I appreciate you guys. |
Beta Was this translation helpful? Give feedback.
-
|
I have a windows WSL setup I'll test with before the next release. |
Beta Was this translation helpful? Give feedback.
-
|
@Alt-168 Its a community Port from PAI 2.4 to Opencode - and it should support WSL out of the Box - there's a WSL Installation Guide also: |
Beta Was this translation helpful? Give feedback.
-
|
Sorry about that difficulty. We are working on it.
…On Wed, Jan 28, 2026 at 5:34 PM, batcountry < ***@***.*** > wrote:
@ danielmiessler ( https://github.com/danielmiessler ) & @ ksylvan (
https://github.com/ksylvan ) , 4 day user here. Just wanted to say thanks
for this work. It has definitely expanded the way I think about this
space.
I wanted to share that I have PAI installed on Windows and installation
was 9 out of 10 difficult. It was a 4-5 hour adventure. I'm quite
technical and would have failed had it not been for the ability to ask
Claude basic questions like "xyz isn't working, go fix.", "check this
again...", etc.
As you think about future versions, how are you thinking about Windows
(WSL) support? (this isn't a feature request, just a Window's user chiming
in so you know we're out here :-) )
I appreciate you guys.
—
Reply to this email directly, view it on GitHub (
#500 (comment)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AAAMLXQT7SCN6ABNCUJHJKD4JFPSZAVCNFSM6AAAAACS7XPOV2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNRTGQ3DCNY
).
You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/500/comments/15634617
@ github. com>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, I was wondering if I can still use the Claude Code subscription for the installation. Since I might not be able to provide an Anthropic API key, I would prefer to implement this through Claude Code. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this does not rely on an API key. We use the "claude" CLI tool, which does its authentication however it does it (in your case, you'll be using your subscription). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone, just wanted to give you a quick update on what's going on.
First, let me formally introduce you all to @ksylvan Kayvan Sylvan. If any of you are Fabric users, he is the MVP for that project as well, and now he's going to be the MVP for PAI!
Kayvan was responsible for professionalizing Fabric, getting a really engineering-focused repo and CI/CD process. And that's precisely what PAI needs as well, so I'm so psyched to have him on the project now!
We have two top priorities which have been spurned on by the very popular Clawd.Bot project. That project made it very clear that having a fast wizard and making things easy to get started is crucial for a project. And it basically is accelerating a whole bunch of timelines for us.
It's a kick in the ass, in other words.
That being said, we are maintaining our previous two priorities just with increased urgency.
PRIORITY 1: Improving the Wizard / Install Process
A much-improved wizard for install and configuration.
I have an idea that I think is going to be really innovative and that I think will get adopted across so much software.
What we are going to do is ask for an Anthropic key in the very beginning. And when we do the install, the file inside of the .claude directory, we're going to launch a full Agent Installer chat interface!
So basically, it's going to be able to ask you Telos questions, help you onboard things, help you find things, help you get stuff from your previous Claude directory, and help you integrate if you have a tricky installation or a different OS or whatever. The most important thing is that we can get the Installer Chat Wizard up and running, and that we have a key. And from there the Wizard can help with so much of it.
PRIORITY 2: Improving the Update Process
It takes far too long for me to go from my version of PAI to a deployment because I have to be so careful about data leakage.
Also, I have a very primitive process for creating releases that is outside of the Git system. And the core problem that this was creating is the separation between my version of PAI and the official version of PAI. Which means I would go through and spend a whole bunch of effort working on everyone's hard-fought victories. And I would get them integrated into PAI.
And then when I rolled out a new version in a week or so, guess what? A lot of those changes would get clobbered. That's extremely not cool. Really sorry to everyone who had that happen to them. It is extremely unacceptable and will be happening a whole lot less and then eventually zero times once we get this system implemented.
Essentially, everyone is going to be making changes into the same merging infrastructure into the official repo, including me.
After speaking with Kayvan and him making the recommendation, I'm basically going to be working from staging branches of a private repo that is CI/CD for pushing to the official PAI repo. But all the changes that I'm making on a regular basis will be going there for all the checks and controls and integration work that's necessary to prepare for PRs going directly into PAI officially.
The other thing we're going to get from this much improved CI/CD system is automatic documentation like Kayvan has implemented for Fabric.
As we push updates, all the documentation everywhere will get updated.
Also related to this, just as an early fix we're going to make, we're going to standardize on a bunch of stuff under
~/.config/PAI/for configuration and such. Which will be nice.--
Anyway, that's just a couple of things that I wanted to let everyone know were the priorities, along with the welcoming of Kayvan to the team officially.
I also know that there are issues and PRs adding up, which we're going to be getting into here very shortly. Fixing issue #1 and #2 is going to help address a ton of those, as well as a lot of the stuff that's already been done likely addressed a bunch of those as well.
Thank you so much for all of your comments, issues, and PRs.
It does not go unnoticed by me. I truly appreciate you.
LFG 🚀
Beta Was this translation helpful? Give feedback.
All reactions