I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
Any conversation
pรฉldรกul Telegram, Facebook, stb., de ilyen รผgynรถkรถkkel bรกrki talรกlkozhat naponta, egybลl felismerhetลk, meg is kell ลket szรฉpen jelรถlni, รฉs egyre bรฉnรกbbak a szรถvegรผk is, ahogy megfigyeltem, gondolom, attรณl fรผgg, ahogy promtoljรกk, vagy instruรกljรกk ลket, ha a gazdรกjuk kifogy az รถtletekbลl, a projekt hamar elfรกrad, a bot csak unalmas h#lyesรฉgekre kรฉpes egy idล utรกn
for example, Telegram, Facebook, etc., but anyone can encounter such agents every day, they are immediately recognizable, they need to be nicely labeled, and their text is getting lamer and lamer, as I have observed, I think it depends on how they are promoted or instructed, if their owner runs out of ideas, the project quickly gets tired, the bot is only capable of boring nonsense after a while
New in agenttop.dev : panels open in your . ๐คนโโ๏ธ
โข Any panel can now split into its own pane, live, beside the table.
โข Works with all the popular multiplexers: , , ๐ฎ๐ป๐ฑ ๐ธ๐ถ๐๐๐.
โข run a panel on its own: agent-top mcp, agent-top slow, agent-top fails, agent-top advice.
โ The # MCP panel also lists the orphaned MCP processes that outlived their agent and are still eating memory.
โฆ
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
