s900mhz

I don’t think that’s what he meant. They both are surveillance tools. He’s just upset only one of those is making people advertise their leave in protest.

This is the case for me too. If I try to automate sign in, it trips bot detection. But if I manually sign in then let the agent rip, I'm fine.

IMO It’s not about being trained on the data, it’s more like what do the agents have access to during inference? Can they grep customer transcripts/logs?

I agree, but I made myself laugh pondering a solution to this in which I came up with a Raspberry Pi like device that acts as the loopback for the agent. Always keep it on and plugged in.

I would like to introduce the Grok Box

No one mentioned communism?

I have a similar setup at home, I’m sure you heard this before but I must +1 the Infuse app on Apple devices. It’s a much better client than Jellyfin’s but can connect to Jellyfin server no problem. No plex needed.

Yes! Where it gets really interesting is the scenario in which every developer has their own unique review skill/workflow, so the reviews end up being different than you running it yourself, but nobody is reading them still.

Thank you!

This is awesome!

I hope they can restore the cartoon cartoon summer resort games.

Has 5.1 reliability improved? I would love to use it again. The inference was just too unreliable when it was first released.

Yes this is the path I’m taking. Experiment, build your own toolbox whether it’s hand rolled skills or particular skills you pull out from other public repos. Then maintain your own set.

You do not want to log in one day to find your favorite workflow has changed via updates.

Then again this is all personal preference as well.

Looks like the repo is very young.

First thing to do is try it out in a hobby project see how it works out!

I find it useful to make Claude track the debugging session with a markdown file. It’s like a persistent memory for a long session over many context windows.

Or make a subagent do the debugging and let the main agent orchestrate it over many subagent sessions.

I was doing the same, but recently I noticed that Claude now writes its plans to a markdown file somewhere nested in the ~/.claude/plans directory. It will carry a reference to it through compaction. Basically mimicking my own workflow!

This can be customized via a shell env variable that I cannot remember ATM.

The downside (upside?) is that the plan will not end up in your repo. Which sometimes I want. I love the native plan mode though.

Why not? If one of your goals is to try to relax and/or meditate more, then I feel it’s a valid list entry.

It’s all a matter of perspective and personal goals, no?