You'd think that if they were compute-limited ... Trying to get people to use it less ... The rational thing to do would be to not ship features that will use more compute automatedly? Or does this use extra usage?

▲

dpark 4 hours ago | parent | next [-]

They are more worried about building a moat than anything else. They want people building integrations that are difficult to undo so that they lock into the platform.

	▲	stavros an hour ago \| parent \| next [-]
		So basically what happened: 1. Anthropic realized their models weren't enough of a moat. 2. They built tools so they could expand their moat. 3. People don't want to use their tools, they want their models, and use other, better tools. 4. Anthropic bans the use of better tools, taking advantage of their model superiority to try to lock people into subpar tools. "I don't have enough of a moat so I'll use my little moat and pretend it's a big one" doesn't sound like a great strategy. All they're doing with this anticonsumer behaviour is making sure that I'll leave the moment another model works for me as well as Claude does.
	▲	lostmsu 3 hours ago \| parent \| prev [-]
		> They want people building integrations that are difficult to undo so that they lock into the platform. Ironically, they are now playing against their own models that can relatively easily build wrappers around any API shape into any other API shape.

▲

whicks 6 hours ago | parent | prev | next [-]

I would imagine that this sort of scheduling allows them to have more predictable loads, and they may be hoping that people will schedule some of their tasks in “off hours” to reduce daytime load.

▲

andai 6 hours ago | parent | next [-]

It also beats OC's heartbeat where it auto-runs every 30 minutes and runs a bunch of prompts to see if it actually needed to run or not.

▲

pkulak 6 hours ago | parent [-]

Man, this just bit me too. I started playing with OC over the weekend (in a VM), and the spend was INSANE even though I wasn't doing anything. I don't see this as very useful as an "assistant" that wanders around and anticipates my needs. But I do like the job system, and the ability to make skills, then run them on a schedule or in response to events. But when I looked into what it was doing behind my back, 48 times a day it was packaging up 20K tokens of silly context ("Be a good agent, be helpful, etc, for 30 paragraphs"), shipping it off to the model, and then responding with a single HEARTBEAT_OK.

Luckily you can turn if off pretty easily, but I don't know why it's on by default to begin with. I guess holdover from when people used it with a $20 subscription and didn't care.

	▲	stavros an hour ago \| parent [-]
		If you want something more lightweight, I made one that has no heartbeat by default: https://stavrobot.stavros.io. It's very light on token usage in general, as well.

▲

pletnes 5 hours ago | parent | prev | next [-]

Also you can schedule it a bit off. Every hour? Delay it a few seconds. Can’t do that with a chat message. Also, batch up a bunch of them, maybe save some compute that way? Latency is not an issue.

▲

ctoth 6 hours ago | parent | prev [-]

I thought about that but I'm pretty sure that if the backlog is automatically clean and I don't need to run my skill for that when I start up in the morning that just means I can do the next task I would have done which will probably use Claude Code.

Your own, personal, Jevons.

▲

iBelieve 6 hours ago | parent | prev | next [-]

Max accounts get 15 daily runs included, any runs above that will get billed as extra usage.

▲

AlexCoventry 5 hours ago | parent | prev | next [-]

I don't think "usage" is exactly the metric they're going for, more like "usage in line with our developmental strategy." Transcripts of people using Claude to write code are probably far more valuable to them than transcripts of OpenClaw trying to set up a calendar invite.

	▲	fgkramer 5 hours ago \| parent [-]
		I mean, they don’t train on your data unless you have the setting enabled. Do you really think they are reading your prompts at all? Free inference providers sure, but Anthropic?

▲

dockerd 6 hours ago | parent | prev [-]

It's how they can lock more users into their eco-system.