@tekmidian/pai 0.40.0 → 0.40.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,22 +1,20 @@
|
|
|
1
1
|
# Provider Independence
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
I started my Thursday at 5am, which is normal — and at about 80%, which is not.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
Because those 80% are not motivation (that was certainly higher). That is the weekly usage of my Claude Max 200 subscription.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
With still two days to go, I was getting worried. Last week I had already hit 100% hard — despite all my efficiency gains, including creating my own "Agentish" language.
|
|
8
8
|
|
|
9
|
-
I
|
|
9
|
+
At 9am I was above 90%, and there was no way I would make it through to Saturday 8am, the weekly reset.
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
So I decided to solve this problem. At 10pm I am at 97% — and that number has not changed since noon.
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
This page shows how to become provider-independent. How to free yourself from Claude, so a maxed-out subscription stops being your problem. How to use any cloud model and any local model inside your Claude Code (or OpenCode) harness. How to run models in parallel, each for what it is good at — all purely local, without resorting to yet another Hermes-or-whatever harness. How to have workers run by default, visibly — and how to interact with each of them in its own chat.
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
My whole journey into PAI and AIBroker started nine months ago, when I used OpenClawd for four hours and had burned through all my credits. I decided then and there that there had to be a better way: instead of API tokens, use the Claude Max subscription I was paying for anyway.
|
|
16
16
|
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
This is how I did it.
|
|
17
|
+
Nine months later, I ran into the next wall: maxing out the Claude Max subscription itself. So the next level of independence was required — and I made that happen, today. Here is what happened.
|
|
20
18
|
|
|
21
19
|
I made myself independent of Claude and Fable. They are great — but I hate being locked in, and I suspect most of us do. I want to decide which model I use: Claude, GLM, Grok, whatever. I need to abstract away from that choice.
|
|
22
20
|
|
|
@@ -35,18 +33,7 @@ So the requirements were:
|
|
|
35
33
|
|
|
36
34
|
The whole implementation cost 7 of my last 10 percentage points of Claude Max 200. Then I switched to GLM for everything else. And what can I say — it works beautifully.
|
|
37
35
|
|
|
38
|
-
---
|
|
39
|
-
|
|
40
|
-
The rest of this page is the operator's guide: switching providers, starting sessions, and the three copy-paste steps to your own setup.
|
|
41
|
-
|
|
42
|
-
> My AI budget hit 91% before lunch. So I changed one rule: the expensive
|
|
43
|
-
> assistant keeps the thinking, a cheaper crew does the building. The feature
|
|
44
|
-
> shipped anyway.
|
|
45
|
-
>
|
|
46
|
-
> Your AI bill is not a fact of nature. It is a design decision.
|
|
47
36
|
|
|
48
|
-
Your assistant runs its helper crew on whichever AI provider you choose —
|
|
49
|
-
and so can the session itself.
|
|
50
37
|
|
|
51
38
|
## Switching
|
|
52
39
|
|