@elvissun My self repair agent is Panacea - she runs a heartbeat scan for issues and errors, has built an understanding of the system, keeps some documentation up to date, has access to all logs including langfuse and can fix small things in code herself. Best investment ever.
@openclawlabs@jdrhyne@Xdiep4474@openclaw I think in some senses moltbook represents this - and it's how our memes emerge, more interest == more activity. But I agree, a more formalised approach I think is under-valued right now.
@seezatnap@emollick Context management works better this way too, the higher up the chain the higher level the context is about the project, and agents can query up or just focus on their piece. Org structure is important and now we can spin up, reshape and tear down at will
@seezatnap@emollick Agreed fwiw - my orchestration is tickets on a board with a team lead responsible for other agents, and more subtasks definitely degrades at a certain complexity - but also handoff and control of a single task is easier this way. It's fractal - then my coders have subagents
@perrymetzger The beginning of the internet was like this, but without the global awareness - students were graduating and looking for ISPs because they couldn't live without, meanwhile the rest of the world was unimpressed. It's louder and maybe faster, but similar. Never stops being weird.
@rishdotblog Guardrails let you go faster - your concerns move from "build this code" to "build this system that lets my co-founder YOLO stuff safely". It's the age of automation and pipelines and resilience, welcome to platform work ;)
@jakeboggan@chrispisarski The key here is these teams have been underserved for years - required to use whatever the saas gave them rather than what they precisely want, and now they can build that specific thing. They need saas, but they're no longer bound in the feature request cycle like before
@imbktan If your engineer is the only thing standing between your codebase and disorganisation, then you have a problem over the long term. AI is a forcing function for better engineering hygiene.
@unclebobmartin@mischavdburg From experience the places AI fails to understand the code are different - there are particular patterns of use it will get hung up on. I have no problem getting AI to understand bad code, but sometimes it will just outright fail on particular concepts, and I tend to dodge them
@esrtweet Use them as a backdrop - humans realise and setup a multi-generational attempt to communicate, the story then is the human drama that unfolds around that process over time. Can tell a story of politics and social upheaval with the Oort communication as a hub to the story
@RobertHaisfield@voooooogel This is something I strike in my own agentic system - I think it's easy to reason around eg tasks and persona as tho they're human, I think when you introduce "I can clone/rewind/alter that person and their timeline" our intuition for good workflows struggles a little more.
@kieranklaassen My ticketing system tends to naturally create hybrids of these - a cluster of child tasks, some in parallel others waiting until some are done. Don't often get the parallel to aggregate naturally, but might add that to prompting