lukasco

9 ms·

1.
by lukasco 13d ago
Guilty as charged.
2.
by lukasco 13d ago
probably the cause, because AGI still can't get releases right.
3.
by lukasco 13d ago
Codus interruptus
4.
by lukasco 1mo ago
Interesting. I feel like Cloudflare is also having a good go at the same target, though from the infra direction. Doesn't stop Stripe of course.
5.
by lukasco 1mo ago
One thing I found was tool calling in GLM 5.2 on github using Claude Code was mostly failing then fixing. But I didn't compare to z.ai's harness. (Nothing to do with Deepseek, sorry.)
6.
by lukasco 1mo ago
Does this solve the problem of which sessions are running what? I have the challenge all the time.
7.
by lukasco 1mo ago
Interesting points. Building on your "bits of freedom" point, given they are doing this to comply with the EU AI Act, it's also possible that the algorithm is quite weak. And they could play all kinds of games, such as embed
8.
by lukasco 1mo ago
I've been building a triage agent for my inbox and whatsapp (it's product shaped), which has ironically left me not building one of these. So even while productizing, I'm getting fomo on the full monty. I've also been bu
9.
by lukasco 1mo ago
I've been running auto-mode for quite a while. The main thing that pushed me over the edge was constantly being prompted in the accept-edits mode because of back ticks or backslashes in tool calls. There was no way to approve those pre
10.
by lukasco 1mo ago
With self-driving agents, the costs stop being evident as you go, and show up after the fact. I've been building governors that slow the agents down, and then also look at odd things some of the harnesses do, such as constantly making
11.
by lukasco 1mo ago
This is one side of the problem: where does your agent show up. And the other side is: where does the agent run And the third side ;-): security. Well done on this bit. I like the smooth onboarding.
12.
by lukasco 1mo ago
Thanks, but I did read the policy. This is what they say: "It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create." And later: "There are very strict guidelines on
13.
by lukasco 1mo ago
I think LLM policies which ban usage are ultimately self-defeating. They neatly switch concerns about quality of contributions to concerns about "AI slop". These two things are not the same. But the biggest problem is that they ig
14.
by lukasco 2mo ago
> Would love to see a 'QM vs Cowork' comparison! It feels like the big thing they are touting here is the shared company brain. Not clear to me though, how that brain is developed when each person has their own harness. (I did
15.
by lukasco 2mo ago
Do you mean using open source models via something like OpenRouter, or do you mean self-hosting the models? That self-hosting bit is definitely something I'm interested in, but it still seems very fiddly (in general). I've had goo
16.
by lukasco 2mo ago
For my autonomous agents, I'm using Github Issues as the UI. And yes, I know this is a total abuse of what a github issue is supposed to be. But it's better than spinning up an ephemeral web site, or hooking into Slack or Telegram
17.
by lukasco 2mo ago
Can you be logged into two accounts at once? It's not the switching, but the different sessions on different accounts that I find myself doing. As some have said, easy enough to build yourself, but I think it' nice not to have to
18.
by lukasco 2mo ago
It's that pesky ban vs enforce ban dichotomy.
19.
by lukasco 2mo ago
Author here: My first version ran alongside my Claude Code subscription, and pretty much banged through my entire weekly subscription in a couple of days. So I bought a GLM subscription and ate through that at the same pace (even though I o
20.
I've been building an agent to maintain my apps(medium.com)
2 points by lukasco 2mo ago|1 comments
21.
by lukasco 2mo ago
Shipping a lot faster definitely puts a big strain on the QA side of the house. But I'm not at all convinced that things have gotten worse even with "AI slop". CI/CD and releasing features more quickly has long been prov
22.
by lukasco 2mo ago
I still find it hard to develop harnesses because you can't really test many turns with an llm in the middle. I suppose doing LLM as judge is one way to start to tackle this kind of thing.
23.
by lukasco 2mo ago
I feel like in some ways this problem is starting to self-correct, sadly by creating the dead internet. If there's no business model to creating content since it will get scraped, then no content will get created.
24.
by lukasco 2mo ago
So many comments here talking about the downsides. The only reason to do a rewrite is because there are massive upsides. Maybe the implicit point is that the upside (memory safety must be the biggest), isn't worth the downside (lots of
25.
by lukasco 2mo ago
Quite a lot of projects are trying this "rewrite to a new language using LLM", both internally, or externally (like is here). For me, they confirm some (slightly controversial) takes. 1. human code reviews are dead. We don't
26.
by lukasco 2mo ago
This is the real problem with LLMs. There is no way to separate code from data. At best, models could be trained on tokens that indicate untrusted data coming in. But then the untrusted tokens could also be messed with. I've wondered i
27.
by lukasco 2mo ago
I mean, I'm guilty too. Claude code scrapes everything in sight whenever I search for something. I've written a small tool to query Github to see if a particular feature has been released for an open source project. I had to use a
28.
by lukasco 2mo ago
Cross platform building and packaging in C/C++ is such a hot mess. There's so many dimensions to unpack I don't even really know where to start. (I say this as the person who has been packaging GIMP for Mac for the last good
29.
by lukasco 2mo ago
Same here. Before auto, couldn’t handle the constant stopping because of backslashes no matter how many things I permitted.
30.
by lukasco 2mo ago
Yeah, that looked pretty cool. But I’m always sceptical of these announcements until I try them.

More ›