The -p flag should be fine, so long as you don't use their oauth in a third-party tool. Gemini also supports A2A for this sort of thing.

▲

gck1 4 hours ago | parent [-]

But the question is - why is the -p flag fine? It hits the same endpoints with the same OAuth token and same quotas.

Comments section here and on related news from Anthropic seems to be centered around the idea that the reason for these bans is that it burns tokens quickly, while their plans are subsidized. What changes with the -p flag? You're just using cli instead of HTTP.

Are the metrics from their cli more valuable than the treasure trove of prompt data that passes through to them either way that justifies this PR?

	▲	NitpickLawyer 2 hours ago \| parent \| next [-]
		> Are the metrics from their cli more valuable than the treasure trove of prompt data that passes through to them either way that justifies this PR? Yes. The only reason they subsidise all-you-can-prompt subscriptions is to collect additional data / signals. They can use those signals to further improve their models.
	▲	adastra22 3 hours ago \| parent \| prev [-]
		Because the ToS explicitly says the -p flag is fine, but the Agent SDK is not.