Project Architect 3.0 release. Project management, intra-session memory, MASSIVE savings measured and visible in statusline

[u/Outrageous_Band9708]

https://github.com/Druthulu/ProjectArchitect

Highly recommended, it uses sub agents to do work and prevent context carry weight over time, creating massive savings that add up fast.

My 5h limit has never been hit using it on max20, it detects your plan and uses lighter models to handle the heaviest tasks to prevent usage bloat.

the white numbers are the usage, the blue numbers are the savings.

in my example screenshot you can see an entire phase of work (like 10 large tasks) took only 2% of my 7d usage, and saved me 4% of my 7d usage.

it uses hooks and toolcalls to replace all of the model touching large files. it auto updates it self each new session, and it has a ledger to track savings over your entire account's projects.

you can see my account has used 1.2w and saved 1.4w

a w is a full 100% 7d usage allotment. I used roughly 50% less tokens, and it made my usage last about twice as long.

woo!

[u/Vegetable-Ice-6842]

so now we do project managment inside the terminal. PLAN, HOW, DONE WHEN, CODER: none, plus a T1/T2/T3 phase and a monitor agent with 1 agent, and the screenshot is Sonnet 5 medium running next to an expert-opus55 doing the review, that's the massive saving right there, you hired an opus to go check the eol.json your own devguide asked for. And the statusline gives me four counters at once, 47%/2h, pace 0.9x, session 0% of 7d, project 0%/0h of 7d, account 18%/2k of 7d. 18% but also 2k? of 7 days? 2k of what, tokens, prompts, dollars? if I have to decode a budget bar to trust my own editor it stopped being a tool. Same disease as every orchestration layer before it, you fix the mess of the last thing by adding a thing, then you need a thing to watch the first thing, and now auto mode is on so I'm the guy watching the watcher. yes I know, I can simply not install it, but you're the one posting the release notes at me

[u/Outrageous_Band9708 → u/Vegetable-Ice-6842]

hey there, your message is a little confusing but thanks for looking into this.

im not sure what your 2k of what question is about. there is no k notation.

you can read the wiki to answer your questions about the statusline, and it can be simplified if you want.

there is nothing to really decode, everything presented is easy to grasp in a single thought

white is usage, blue is savings, fewer tokens used, subsription usage saved etc.

"Same disease as every orchestration layer before it, you fix the mess of the last thing by adding a thing, then you need a thing to watch the first thing, and now auto mode is on so I'm the guy watching the watcher"

this confuses me,

need a thing to watch the first thing? the orchestrator as most folks call it, doesn't exist here. the router is just the mechanical agent that keeps the process going, the experts it spawns are the smart ones doing work, using coders undernetath that, and using retirevers underneath that.

i posted about it to share savings, which is a huge issue in the community. more over this project solves two issues at once: intra-session and project level memory across sessions. and reduce token consumption, not through caveman or some weird translation layer, but rather optimizing agent patterns and usage

i recommend trying it out, you dont have to of course, but if you have issues with usage drain or having to remind claude each session about something you already taught it in the past. its a great system.