u/Ok_Veterinarian_6364

some extensions expose 30+ tools setActive by default, always on, bloat the context w things 99% of the time llm does not need to care about:
- load all tools desc on system prompt -> pollute every turn
- also the api payload json for all
- 1 - 2.5k token every turn
- inject and hijack user prompt EVERY TURN with tool usage remindser - another 200 - 1k tokens
- this adds up when we install more ext
- e.g: for me, just 2 simple packages bloat the context every turn ~10k extra junk text (3.5k tokens)

i know prompt caching, 1M context for a ton of wrapper shit, and stuff.
==> but why do they do so? lazy vibe coding? or there are reasons?

imo, there are better approaches:
- expose min active tools to llm: only core stuffs that llm should auto call
- a skill.md to desc all other shits - 1 fronmmater, contain all tool desc n usage, llm reads only when relevant
- a simple /command toggle setActive
- set all user/manually trigger tools to /command - things llm shouldnt care about, let user decide
- Skills are standard for agent nowadays

- e.g: pi-subagent:
+ 1 active tool
+ 1 skill.md
+ ton of shits llms should give a f -> place in skill.md
+ some /commands for user to trigger
--> still works flawlessly even w cheap models, small context window

thought? i have to miss something here otherwise i have to audit every extension i installed and manually patch them to not let my Pi become HERMES AGENT

multi-purpose agent, not just a coding agent.

tried to bridge to telegram, takes time to tweaks for full TUi slash command support. noww i just use termius to chat w Pi.

next i will make a cron extension, and a good memory management.

and i think its good to go! any recommendation?

im planning to use pi-subagents for tasks
i want to keep my Pi lean and lightweight. just minimum ext/skills for everyday agent!

happy w my Pi journey so far! it takes more time tinkering vs hermes but its worth it!

im tweaking lllabs pi-telegram bridge
idk the proper way to patch it

ussue: pi-telegram only support some fixed commands, and many TUI slash commands like /new, /reload, or ext/ commands wont work

im patching it in my way: try to fetch all commands on pi startup, try to parse "/" telegram message as TUI naitive commands.. but no good results yet (i thought it was simple so i let DS do it and it failed)

i tried other extensions - commands wont work on telegram also

anyone has a proper solution for this?
not just Pi naotive TUI commands
e.g: i made a /chat to toggle chat/exec modes. it dont work via telegram after some tweaks from DS

i love Hermes. i even cancelled all frontiers to use it everyday - daily logs, todo list, crons, code.. all day long.

but i have to admit there are 3 things i dont like:

- sh ton of token overload

- auto memory and skill creation: i have to turn them off. The concept is promising.. but.. llms ain that good yet. agent made skills and memories full of context bloat, pollution, hallucination. after daily maintain these things for a month.. i give up.

- Too hard to tinker: i have to patch its source code to turn the auto skill/memory off. not a problem, but then i realized how many hidden/system prompts wrappin around Hermes.

after some tweaks, i thought: ok, i jumped from oc to hermes for a production grade agent, however if i have to tweak this much, i would just use something else - minimal, then build from scratch.

its just me dont know how to custom it. Help, and pls share your thoughts

so beautiful! i used many harness ones - claude vscocde, cli, codex.. but i love opencode the most!

anyone else?

hope this open source thing grows and become a thing in the future - opensource, open w cheap models, reasonable sub plans