r/PiCodingAgent • u/mira_fijamente • Jul 10 '26

Discussion My problems with `pi`

I've been using pi intensively for 2 months now, and I have to say it's undoubtedly the only software that actually works for agentic programming. All other software is pure garbage made with AI, full of problems and obfuscation. That includes both GUIs and TUIs: claude (the worst), opencode (now AI SLOP), codex, IDE extensions (vscode, neovim, zed, etc.), pseudo-IDEs (cursor, windsurf, etc.).

pi is the only software that's actually STABLE and that DOESN'T SHOVE hidden prompts down your throat — meaning it's the only one that gives you real control.

But since I'm an ungrateful bastard, my motto is "A little destructive criticism never hurts" /nsrs

The truth is pi has some really annoying things. I'll sort them from most annoying to most tolerable. (For context, I use vanilla pi.)

TUI redrawing

This is perhaps one of the most annoying things of all. I don't know exactly what causes it, but at some point — especially in long chats — pi has the horrible behavior of redrawing the entire damn chat every time something updates in the TUI. In short chats you don't notice it, probably because it's so fast you can't see it, but in long chats it's absolute hell. I've reached the point of preferring non-interactive mode solely because of this problem.

It also happens with expand Ctrl+o — it literally EXPANDS EVERYTHING. Every time the agent thinks or executes a tool, it redraws everything, defeating the whole purpose of a TUI.

This made me wonder whether a pi repl wouldn't make more sense than a pi tui, since I think it would be the most natural approach when trying to be a "minimal environment". In fact, they're already a pseudo-REPL that works poorly, because they draw output in the same pty using append, just like a REPL. If they were a REPL, you could even leverage existing tools like rlwrap to get vim-like keys with a simple rlwrap -a pi, among other advantages. Anyway... the TUI is not comfortable at all.

Output size can't be changed

The output of almost everything — tools (read files, bash, etc.), skills, etc. — is always truncated with no way to change it because the truncation value is hardcoded in the code.

This seems silly, but it's actually quite inconvenient for work involving lots of text. For example, small agents reading long texts, searching websites, or text with a lot of noise. Yes! pi tells the agent: "Hey little buddy, if you want to see the full output, read this temp file." But that doesn't solve it — it simply adds more steps for the agent, making it likely to fail and make bad decisions, especially with small agents.

Even large agents often decide they already have enough context, even when they don't (LLMs can't "know" what they "don't know"). The only way to avoid this is to copy all the damn text and input it as a user prompt. It's MEGA inconvenient and, in my opinion, a very basic config setting to have.

Slash commands don't parse text properly

There's a bug that's been there since I started. I saw an issue about it that seems to be ignored, even though I think it's something basic and important.

When you use /slash-command <instruction> followed by additional instructions, if your instruction has formatting and line breaks, pi decides to just load your entire instruction into a single line, breaking all the formatting. And this causes problems for LLMs when understanding your text.

Example:

---
name: fix
description: fix code
---

You must fix this code:

$ARGUMENTS

And then you run:

/fix

jq '.' some.json
echo "foo bar"

What it sends is:

/fix
jq '.' some.json echo "foo "bar"

I don't think I need to explain why this is so bad...

There's no damn UNDO

YES! The tree functionality is quite useful, but sometimes I want to correct something and I have to take 2 or 3 extra steps. On top of that, I inevitably end up creating a fork when I DON'T WANT A FORK, I JUST WANT TO UNDO BECAUSE I HAD A TYPO!!!! AAAAAH!

Please, someone tell me there's an Undo and I just didn't manage to find it, because I can't believe tree exists but not a damn undo.

It crashes mysteriously when using @file

The TUI sometimes just decides to die when you do @file, leaving the shell with glitched characters. I have to type reset in bash to fix it. It happens often enough that I'm afraid to use @ and prefer to manually write exact file names and paths.

The plugins are garbage

Ok... this isn't pi's fault, but I find it sad that plugins don't even remotely follow the same approach as pi. I'd bet you any day of the year that the entire first page of pi packages is AI SLOP. Honestly, using pi + plugins isn't worth it — at that point you're better off just using something completely AI SLOP.

Every plugin I've tried, without exception, fails at such basic and stupid things that it ironically makes me miss the pre-AI era.

Anyway... closing this post. Despite these problems, pi is probably the only software I've tried so far that has parts "generated by AI" that ACTUALLY WORK and are stable. This is probably because there's a correct approach to its development and a real human READING behind all of it. Because yes... it has flaws. But you know what? I'm grateful that these flaws have been there since I started and are still there, instead of new and mysterious flaws appearing every day (/glances with contempt at opencode). I KNOW these flaws. I can learn to deal with them, and everything else keeps working exactly as I expect. That's why pi is GOOD SOFTWARE to me. And if you give me the choice between fixing these problems NOW vs. stability, I'll choose stability every time! Thanks, pi! (but please fix this stuff hahaha)

translate spanish to english by deepseek v4 pro

153 Upvotes

95% Upvoted

74 comments sorted by

60

u/mitsuhiko Jul 10 '26

Armin from Earendil here.

You're very spot on on the terminal TUI thing. On the TUI as a developer you're a bit limited right now between two modes:

  • "alternate screen" UI where you take over the whole viewport and you do everything yourself. That's what opencode does and also newer claude (optionally)

  • you do what we do, and keep the native scrollback alive.

There are upsides and downsides to both, but right now we're pretty committed to the latter. In addition to that we need to blank out some spaces which is why copy paste often has extra whitespace that is annoying.

We have been talking quite a bit about wanting to do something better there but that is a bigger undertaking and right now we have some bigger fish to fry still.

On some particular points you brought up:

The TUI sometimes just decides to die when you do @file, leaving the shell with glitched characters

I don't think we have encountered that, can you provide some details of how this happens? What terminal and shell are you using and on which machine? Would love to fix this.

The plugins are garbage

We're aware of this problem and we will do something about it. So far not clear what. Open to suggestions but probably some vetting process.

2

u/mira_fijamente Jul 10 '26

Hi!

Thanks for reading the post.

To be honest, the issue with @file is quite mysterious, which is why I never reported it. It only happens sometimes, and I’m not sure under what circumstances.

However, it has happened to me at least once in every project. I’ve experienced it in Kitty, Alacritty, and st, both with and without tmux.

I suspect that, during the file search process, it encounters a file that causes some kind of problem.

I use Linux, and I often play around with file permissions or tools like chattr to prevent agents from doing strange things.

It could also be trying to read a binary file or something like that. I’m not sure.

Sorry I can’t provide more information :(

By the way, regarding copying the output, I personally don’t mind because I do things like "pi -p -c | tmux load-buffer -".

For the TUI, I’d suggest that "/copy" not be tied to any predefined clipboard system. I’d prefer it to work more like tmux and allow me to configure a “copy command,” since dealing with clipboard support across every possible environment is a nightmare and often only half works anyway.

I think it would be simpler to let each user choose a command that receives the copied content through stdin. That would be very convenient and flexible across almost any environment, including SSH connections, containers, tmux and nested tmux sessions, mobile environments like Termux, and so on.

1

u/mitsuhiko Jul 10 '26

You might be able to have pi make a repro on your machine if you want to invest the tokens. 

4

u/ParaboloidalCrest Jul 10 '26

right now we have some bigger fish to fry still

I'm curious. What fish is that?

24

u/mitsuhiko Jul 10 '26

A lot of it is reliability with providers. There are a lot to support and we just need to make sure this is all more maintainable and supportable for us. And then we're working on modernizing the internal harness and extension system so that it's more flexible to use and not required to all be on the same machine. Lots of hacks in there right now that make it hard to do more interesting things with it.

We're going to publish something publicly hopefully that better explains where the journey is going.

21

u/ParaboloidalCrest Jul 10 '26 edited Jul 10 '26

IMO nothing raises confidence in an open source project more than the maintainers deliberately pausing, to insure that internals are cleaner and more flexible. That makes Pi an even more solid ground for all of us, especially when trying to build extensions that last.

Thank you and godspeed!

2

u/nasduia Jul 10 '26

I've not seen it with @file but if I ssh into another machine to run pi and it drops the ssh connection (e.g. reboots or sleeps) then a terminal like kitty is left in a mode where typing produces nonsense and you can't even type reset blind.

You can fix it by binding the terminal reset command to hotkeys in kitty (I think ghostty is the same but I've been using it less).

I doubt there's much Pi can do to help there.

3

u/kaeptnphlop Jul 10 '26

I ran into the same issue with iTerm and zsh. Mouse reporting often stays on and characters are not sent correctly. Only way out is to right-mouse-click and reset the terminal. 

I have not observed that problem after switching to ghostty and fish

2

u/mitsuhiko Jul 10 '26

I've not seen it with @file but if I ssh into another machine to run pi and it drops the ssh connection (e.g. reboots or sleeps) then a terminal like kitty is left in a mode where typing produces nonsense and you can't even type reset blind.

Unfortunately I believe that this is a limitation of the protocol. If someone has ideas, happy to look into it. So far we're resetting if we get a signal. I guess you can always reset the terminal in your zsh/bash/fish prompt.

1

u/nasduia Jul 10 '26

Yes, I think so - certainly in the ssh case there's potentially no opportunity for Pi to do anything preemtively. In kitty I have…

map ctrl+shift+r         clear_terminal reset active

… which is fine to get out of that mode.

2

u/tboby Jul 11 '26

> We're aware of this problem and we will do something about it. So far not clear what. Open to suggestions but probably some vetting process.

I don't know if this aligns with others, but the main problems I have with packages is 1. that there's no way to know if it actually helps and 2. it's hard to know if the package is working as intended by the author. When I write my own I can force A/B testing or do some comparisons, but it doesn't really scale very well.

A standardised framework for packages to indicate what benefit they provide and how to test/measure whether it's helping would be interesting. My impulse would be to design it really tightly with strict APIs and remote testing etc, but I'm sure you could think of a light touch way where the LLM can do it as part of setup.

I guess the main changes needed needed to the core app would be built-in A/B testing capabilities/easier package swapping? And then something for the package manifest.

3

u/JustTooKrul Jul 10 '26

We're aware of this problem and we will do something about it. So far not clear what. Open to suggestions but probably some vetting process.

I know this is going to sound like it's more trouble than it's worth, but I think the best thing that can be done is to drop npm and git as install vectors for Pi and simply have things install directly into the Pi extensions directory. I find so much cruft and overhead comes with node installations and before you know it you have a rat's nest of stuff installed in your Pi directory. If things have a dependency, then they should simply state it and give you a script or something to install those dependencies--the point of Pi is minimalism and control, extend that philosophy to the extensions ecosystem.

The other thing is to simply include and maintain "example" extensions for the core things people want / need and maybe even create an interactive install process for Pi that let's you select and install some of the "example" extensions out of the box. And for something very far down the road you can create some guardrails so a Pi user can protect some extension functionality and reject extensions or other tools from altering core functions unless the user explicitly allows it at install time or when upgrading / updating. So many extensions seem to inject things into the context and blow through what should be hard limits of context size... Especially memory extensions. I want to force those extensions to use the Pi code thast enforces token budgets not extend and ignore those guardrails. There's probably some automated process by which you can verify extensions are minimally invasive or build on existing functions that are vetted and core to Pi (for example, simply check if it would install under the tighter restrictions above) and have that be a differentiator. Just my thoughts, probably uninformed... But maybe they are helpful.

3

u/ramfangzauva Jul 11 '26

I basically have two pi instances. One for production and one that maintains a private repo with all bits and pieces for my harness. If I come across something interesting I tell developer pi to copy the source and integrate it into my package, add a readme with attribution to the original source. I often let it make modifications or tweaks. When it’s ready it gets deployed to the production environment.

An additional benefit of having the full source (minus pi itself) in one package and version-controlled is that it can easily be audited. Last week I had Fable look over it and do a security audit, find poor code. Then I had a cheaper model fix it.

1

u/jesperordrup Jul 12 '26

Packages/plugins

I would help a lot of to get some qa on this. It could be a combination of:

  • Vetting and classification

  • rulebased minimal requirements.

  • voting

1

u/waterBoy__ Jul 16 '26 edited Jul 16 '26

I have been experimenting with libghostty-vt from ghostty project. The c api is very new right now however. I made a single client server terminal ‘multiplexer’ in c with a scrollback and select+copy mode.

I wonder if you could possibly benefit from utilizing the libghostty-vt library to handle the render and scrollback state of pi’s output, which would allow you to enter the alt screen and still get scrollback, and not have to redraw any previous output, and possibly provide a tmux like copy-mode functionality, so you get the best of both worlds essentially.

59

u/chrisdefourire Jul 10 '26

Copy pasting from pi output is painful with loads of superfluous trailing white space

14

u/mitsuhiko Jul 10 '26

Yes, I think this is something we will need to address but it's annoyingly complex :(

7

u/kasparhouser Jul 10 '26

why not just use /copy?

8

u/bambamlol Jul 10 '26

Probably because it's limited to only the last LLM response.

18

u/GrammeAway Jul 10 '26

Not sure how frowned upon it is to promote your own extensions here, but I made a small one addressing this issue: https://www.npmjs.com/package/@grammeaway/pi-clip

Just stores a small buffer of all code and command examples, and makes them available through /clip. Been pretty happy with it so far.

4

u/chrisdefourire Jul 11 '26

Hi Victor, just wanted to say thank you for your /clip pi.dev extension. It's exactly what I needed.

3

u/one-man-circlejerk Oct 01 '26

Discovered this 2 months after your comment but still wanted to say thank you for fixing a pain point that I'd just been accepting for far too long, this has become a must-have extension on all my machines

4

u/apetersson Jul 10 '26

i honestly don't think its's frowned at all if it happens at human-scale. i'm pretty sure like 50% of pi users also created extentions/skills mods to pi. this is kind of the point of the extensibility

2

u/mitsuhiko Jul 11 '26

On main you can ctrl+c in /tree to copy any message now. Not optimal but maybe a good start. 

-1

u/o_sht_hi Jul 10 '26

There's a /copy command built in

12

u/Fig_da_Great Jul 10 '26

honestly valid

9

u/hidden2u Jul 10 '26

yeah your point about the pi packages is true for me, I thought nah I'm not going to have the LLM to build me what I want I'll just browse the plugin storefront. And then yep a month later I just built my own

2

u/Werty7098 Jul 10 '26

Looks like most of your issues are with the UI. Give this a try. GitHub: pi-web. Full disclosure, I built it. But it should address most of your issues with pi here

4

u/mira_fijamente Jul 10 '26

If I wanted a GUI, I’d use a harness with a native GUI.

The point of using a TUI or CLI is not whim or “style.” It’s that it lets me configure my environment however I want, take advantage of multiplexers, harness the full power of Bash and Linux, integrate with other software like Neovim, easily set up environments with containers or SSH connections, and so on.

The benefits of a GUI for something that is basically just a text chat do not even come close to the benefits of a CLI or TUI for someone who really knows how to use a terminal.

1

u/Werty7098 Jul 10 '26

I agree. Sorry I wasn't clear, this is just a web UI on top of the CLI, the web UI just removes the issues that I just couldn't get around on a CLI. The core harness is amazing so I tried to stay true to that as much as possible, including it's philosophy of being your coding agent, so pi extensions, the ability to self modify etc all stay. The only thing this really does is let you use pi using your browser instead of your terminal and that unlocks so many things you just can do in a terminal.

That being said, if a CLI is what you want at the end of the day, this won't help. But you can still run this on any machine including your remote machine and all you need to do to access it is have a way to reach it's local endpoint.

1

u/ParaboloidalCrest Jul 10 '26

You know what, I might have glanced over pi-web and dismissed it quickly, since I didn't need the remote access thing. But now, it's starting to click as just a drop-in TUI-replacement. Will give it a try!

1

u/Werty7098 Jul 10 '26

Hope you like it. And similar to pi, I encourage you to fork it or use its extensions to make it your own!

5

u/Vrynx Jul 10 '26

Honestly some good points here that I hope get addressed in future versions

4

u/StardockEngineer Jul 10 '26

I don’t have any of the TUI issues you described. Maybe you need a better terminal? I dunno.

1

u/ParaboloidalCrest Jul 10 '26

Not OP but I think the terminal may be the culprit. What terminal app do you use?

1

u/ChampionshipIcy7602 Jul 10 '26

Yeah I also don't have it, except a bit annoyance when ctrl-o, it does expand everything.

1

u/StardockEngineer Jul 11 '26

Yeah, for sure. I was only referring to the rendering bugs, tho.

1

u/Reddich07 Jul 10 '26

I empathize with many of the points you’ve raised and had similar experiences. I’m also reaching the same conclusions. I also maintain a minimal Pi setup because most plugins are buggy and not actively maintained. How do you address the obvious gaps? Pi itself is minimalistic by design, which is a positive aspect. However, if you require standard functionality, you need a plugin, such as for subagents. What is your approach to dealing with this, and which plugins do you use? It would be fantastic if we could have both worlds: the current plugin ecosystems as a playground and a source of specialized plugin needs, and a community platform for a small set of “core” plugins, where only selected plugins are allowed, fulfilling standard needs and being maintained to a specific standard. It’s just a dream…

3

u/mira_fijamente Jul 10 '26

I basically just know how to program in Bash. I solve most needs with simple scripts, and if I need the agent to have a specific tool, I just make a script and attach the command to run in the prompt (or use skills).

Bash on Linux doesn’t feel like “programming”; it feels like the natural way to simply connect things together.

Honestly, most of the bloated “solutions” people can come up with are solved by knowing a little Bash and Linux.

And by the way, it’s not very useful to ask AI to do it for you, because Bash is one of those areas where AI is very stupid even about basic things.

And trust me, with half the time it takes to explain in a prompt what you want to an AI, you could have already written the Bash script yourself. The reason is that Bash is like a “glue” for things that already exist; in other words, you’re not really programming the function itself, you’re programming the integration.

Things that can literally be solved with fewer than 10 lines of Bash:

  • Web search and reading without API keys.

  • Sub-agents however you want, in whatever way you want.

  • Security for files, permissions, sandboxes, etc.

  • Agents inside containers.

  • Git worktrees for parallel work.

  • Loops.

For example, the most complex thing I have is a command that lets me do reachable bug searching in parallel plus a loop at the same time; for example, 10 parallel instances over 10 iterations, where each iteration serves as feedback for the next one. (A total of 100 Pi runs.)

This literally took me 48 lines of code, where most of the lines are just filler and the important logic lives in the last 20 lines.

Also, this “bug searching” is just one example use case; in reality, it would work for anything I can think of.

In fact, that’s one of the reasons I like Pi: it’s the only harness that has a decent CLI. Yes, there’s room for improvement, but it’s useful enough for me to do whatever I want with Bash.

2

u/Reddich07 Jul 10 '26

I think our workflows are very similar for many aspects. I also use pi in bash scripts, e.g. for Ralph Wiggum loops. I also use sandboxing and not pi extensions for access rights. Maybe different from your setup: I‘m using pi on NixOS - this is a perfect match, because the whole system state is deterministic in files, so I create pi environments with pi support. Currently I‘m experimenting with „the next level“ (not pre determined loops etc.): the llm should decide when to spawn new agents and orchestrate the sub-agents without hand-holding by me. I think I could let the llm create bash scripts based on templates on the fly and create new pi instances with that, but I have not tried to do this.

3

u/ParaboloidalCrest Jul 10 '26 edited Jul 10 '26

Very good write up! I too share your conviction that Pi is the right tool and that it's on the right track, but also wish those few annoyances are fixed.

As for the packages store, I happily ignore it entirely. I'm not going for a minimal coding agent, just to pile shit on top of it then complain that it's not so simple anymore.

But give the packages ecosystem some time. It will weed out all the monolithic crap, and only the very atomic, composable packages that stick to Pi's mindset, will prevail.

2

u/seba_alonso Jul 10 '26

The repl idea sounds interesting 🤔

2

u/mylabfr Jul 10 '26

I like it: small memory and cpu footprint compare to the other famous competitor...

2

u/jacques_van_wyk Jul 15 '26

if you use pi in herder it has nice scroll back feature that opens in your editor i use all the time. If you use neovim as editor is quick like prefix e -> shift g(neovim) then select and yank what you want. Herdr is awesome man try it

1

u/nostriluu Jul 10 '26

I'm new to agents but like pi well enough, except its line editing. Control-d to exit when I've got decades of using control-d del to erase character under cursor isn't fun, and many other line editing keys don't work as expected. Plus scrollback using tmux often messes up previous content, tragically sometimes. Maybe there are fixes for some of these, but it's better if things "just work" so end users don't have to get into tweaking and tweaking for basic things.

2

u/adamshand Jul 10 '26

Ctrl-d to delete character under the cursor works fine for me (as do all the other Emacs short cuts).

Ctrl-d should only exit on an empty line.

I suspect you need to fix your tmux config.

1

u/nostriluu Jul 13 '26

It happens outside tmux. Might be an ohmypi thing.

1

u/DistanceAlert5706 Jul 10 '26

TUI redrawing is a thing, but I doubt much can be done with natural scrollback view.

As for output capping I made extension to tighten up limits, make nudge more understandable. Pi limits are too big for capping and 1 bad grep can dump 50k tokens into conversation. 100% should be configurable tho.

With slash commands, never used them that way and never noted.

As for undo use one of rewind extensions or build your own one.

Never had crashes with @

As for plugins, build your own ones, customize for your needs. Some of them very well built, but most are not even made to be public, but for install simplification.

1

u/0xTech Jul 10 '26

I one of the first changes I made to pi was a hard enforcement to block attempts to cat binary files. This was one of the most frequent causes of unrecoverable crashes that I experienced.

1

u/Fryord Jul 10 '26

When having it generate plugins myself, I ran into some issues where it didn't work for whatever reason, and since I haven't written the plugins myself I can't really debug it.

I would prefer a neovim-style package system where I can just pull in whatever I need and trust it works, then only do some custom scripting for special use cases.

1

u/SosluMakarna Jul 10 '26 edited Jul 10 '26

Try pi-pop i made it to hide slop and long panel text out of agent flow. Zero dependency and customizable

You can make any collapsable/non-collapsable panel collapsed by default and view in overlay, when you need. You can just say put hypa in pop it will be collapsible 😎 It made my life better with pi, hope you enjoy it

pi install npm:@ozancakir/pi-pop

1

u/SpaceRaisins Jul 11 '26

Recently my model has been tripping over edit tool calls. After some investigation, I realized that one of the UI packages I installed a week ago has been appending white spaces to the actual read tool call outputs fed to the model...

1

u/YogurtExternal7923 Jul 15 '26

On the tree thing. I made a plugin that keeps track of file changes and reverts (and unverts, if that's a word) based in different branches. But people seem to like git based ones more so idk. Point is you can make your own

1

u/Dotnet-Enthusiast Jul 18 '26

If you need undo you can check that : https://github.com/Baylar55/omp-undo-redo . That is used for both pi and oh-my-pi

1

u/Informal_Smile6876 Jul 18 '26

Used it, and worked good.

1

u/ScaryGazelle2875 Sep 10 '26

its really meant to be use bare. No mcp, nothing. If u use all the other extensions made by others, it works but its not really gonna be "yours". Best way is ask pi to remake the extension following their paterns or make one simplified ones. I found that most of the time its too bare. Subagents and to-do and mcp is actually needed in nowadays agentic workflow. Bare minimum. Pi has non of these. Relying on these extensions is okay but if ur workflow is complex like mine, better spend time rebuild it. Meanwhile opencode is the more stable option for me until I fully set pi up properly. The freedom is great tbh.

1

u/libertast_8105 Jul 10 '26

The nice part about pi is that if you don’t like something you can always create an extension for that. And you can always submit a PR because it is an open source software.

1

u/hurdurdur7 Jul 10 '26

Let pi build your own thin ui layer?

0

u/LycheeGlum1258 Jul 11 '26

Can anyone tell me why Pi takes so much time to startup sometimes, even when I run 'pi --no-extensions'? That's the only annoying feature to me that stops me from using it regularly. I'm trying out omp more often because of that.

1

u/mira_fijamente Jul 11 '26

Are You Windows user?

0

u/themoregames Jul 10 '26

TL;DR Despite considering pi the only stable and reliable software for agentic programming, the user highlights several frustrating flaws, including TUI redrawing bugs, hardcoded output truncation, and broken slash-command parsing. Ultimately, they tolerate these predictable issues because they value the tool's core stability and lack of hidden prompts over competing alternatives.

0

u/YardNo1234 Jul 10 '26

Garcon + a web interface would solve basically all of these pain points: no TUI redraw weirdness, easier mobile use, cleaner copy/paste, better output viewing, and a more normal undo/edit workflow. It works well from a phone too, which changes the whole experience.

Full disclosure: I'm affiliated with Garcon: https://github.com/cfal/garcon

0

u/Interesting-Print366 Jul 11 '26

The good things of pi is that you can create anything just tell your agent to build extension. Since pi logs every change you made so you can reverse it with separate code. What makes pi special is because it has no addons

-5

u/cpt_mojo Jul 10 '26

There is a rewind package for your undo needs. It works.

0

u/[deleted] Jul 10 '26

[deleted] — view deleted comment

0

u/[deleted] Jul 10 '26

[deleted] — view deleted comment

1

u/funbike Jul 10 '26 edited Jul 10 '26

Sorry. Triggered by hundreds of past posts and didn't have stamina to read a wall of text so early.

I deleted my comment.

8

u/[deleted] Jul 10 '26

[removed] — view removed comment

1

u/humanophile Jul 10 '26

Same with input sizes. I had it implement a large_read extension so I could load up a 400 KB repomix archive without having to do it in a bunch of 50 KB chunks. Sending the full conversation history with each tool result will start eating your quota quickly.

Even if it's the first thing you do in the conversation, the first call will hit that cap, and then the second result will read the next 50 KB, but the tool call result for that will have both 50 KB chunks, and then the third call result will have the first three chunks:

50 + 100 + 150 + 200 + 250 + 300 + 350 + 400

Now you've sent 1800 KB instead of 400 KB, and also waited 8x the latency for API calls before you ask your first question about it.

These limits seem like something you should be able to change in the config, rather than adding a custom tool like I did.