kami23

Been looking forward to this. I'm not up to date on my python and reviewing Claude's implementation of the python library has taught me a lot.

Gonna point Claude at our repo and see if I can do an easy conversion, makes the amount of reviews I have to do a bit more bearable.

Ah cool! Great to see accessibility stuff like this. Listening to papers makes it much easier for me to focus on the content.

I made my own little service that converts any webpage to hopefully the parsed content then uses Google TTS and then published it to a bucket and s3 feed and I listen to them on my phone before bed.

The key for me has been that they are useful when I'm working on a new product or a very very large feature. After I have planned with claude for a few hours to refine architecture and edge cases, my implementation plans are rather large but broken into phases.

I usually ask it if any steps are good for parallel work, and I kick off multiple agents at that point. Each is assigned a phase. They have to work on different work trees in my flow and I've rather disliked it and I wish there was a better way than worktrees at the moment, but I guess people are busy building those tools, right?

Hell, I'm writing a small tool to let me share a Claude session with my team from their own terminals, so that any of us can take prompt control while we work through plannings and implementation. I'm sure many others are finding these needs!

These things not being android based is always a deal breaker for me because I have so many sources of DRMed audiobooks or ebooks that would just be a hassle on a lot of these e-ink devices, which is something I really want out of these note tablets.

I got a boox air note 4c with the original intention of using it for comic books with some basic coloring, but have found it significantly more useful for notetaking over anything else. UX is still abysmal in some ways that make starting notes a chore, but it's increased my note taking and journaling significantly.

That's a similar story for me at $DAYJOB. We have copilot for our IDEs and it is so much worse than Claude code or any other CLI integration option. We're so restricted on adopting the features as fast as they are turned on. I try to use it during the day and end up frustrated that the agent mode is restricted and returns "I can't complete that for you" or something similar when asking for pretty reasonable actions.

I've been cranking out personal apps with Claude Code in contrast and my brain is exploding with ideas for day job, but this is such an organic space that the speed that corporations move at they are using the cool tool from last year has left me demoing personal work to coworkers and hoping that starts to move the needle on getting better tooling. I understand the governance and privacy concerns for $DAYJOB, and as such every tool needs to get approved by a slow human process.

We also have OpenAI access and I have found myself using that for research more so than copilot as well, maybe we just picked the worst tool because of that MS vertical integration...

These are the same categories of coordination I've been looking at all day, trying to find the sweet spot in how complex the orchestration can be. I tried to add some context where the agents got it into a cycle of editing the code that another was testing and stuff like that.

I know my next step should be to give the agents a good git pattern but I'm having so much fun just finding the team organization that delivers better stuff. I have them consult with each other in tech choices and have picked what I would have picked

The consensus protocol for choices is one I really liked, and that will maybe do more self correction.

Ive been asking them to illustrate their flow of work and asking for decisions, I need to go back and see if that's the case. Probably would be made easier if I get my git experiment flow down.

The future is tooling for these. If we can team up enough that we get consensus approaching something 'safe' the tools we can give them to run in dry/live mode and have a human validate the process for a time and then once you have enough feedback move into the next thing needing fixing.

I have a lot of apps with cobra cli tooling that resides next to the server code. Being able to pump our docs into an mcp server for tool execution is giving me so many ideas.

I tried this tonight as my first time using anything like Claude code, and having a week or so of copilot agentic mode experience.

It's the right path, I'm very smitten with seeing the sub agents working together. Blew through the Pro quota really fast.

I was a skeptic and am no more. Gonna see what it takes to run something basic in a home lab, and how the performance is, even if it is incredibly slow on a beefy home system, just checking in on it should be low enough friction for it to noodle on some hobby projects.