its based on my own experience . i tried my openclaw to register to github and it was blocked by captcha and consume all my tokens . we need a different approach for AI agents.
That feature is a friction for agents because without the friction, scams and spam get massively enabled. Calling it the 'agentic era' doesn't suddenly make those desirable things.
If there is a captcha there to block the automated creation of accounts, that it was difficult for you to autonomously create accounts is completely intentional.
> and consume all my tokens
Your bad coding/config (or your agent's bad coding/config) allowing run-away token use, is a problem for you, not a problem for everyone else.
> but we are in agentic era now.
Enabling autonomous account creation will enable a huge pile of spam and scam account creation, we've been in the spam/scam era for decades and it will not be over in the foreseeable future, your agents will have to put up with that just like us humans do.
> that feature is a friction for agents
[reaches for microscope to aid playing the appropriate violin]
> this validates the thesis and narrative of agentic first git platform
Perhaps your next thesis should be the result of a project where you design and fully verify a system that will solve the spam/scam problem that enabling your use case will also enable, instead of just expecting the world to make all the effort of rearranging itself around the way you want to work.
Automated account creation is quite likely a direct breach of their AUP anyway, maybe you should instruct your agents to check such things and try not to do things that are in direct contravention of the rules of the tool they are trying to use/abuse.
--------
If your response to this is “Fine, our agents just won't use your systems then.”, then that is great: The system works!
Really all you need is a good cli. Agents I use have no trouble with gh or glab or tea. Clicking on this git platform idk what the hell is going on. I clicked on one repo with random letters in the title and it was empty. Womp.
> you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a portmanteau to refer to a product or service's use of Git code.
> Please be aware that GitHub and GitLab are exceptions to this Policy because they are subject to explicit licensing arrangements that pre-date, and thus take precedence, over this Policy.
There's a lot of tech stack jargon here that it doesn't really tell me what it actually does. How does this differ from me using an agent with Github's MCP to control my repo?
Maybe they're going for the "PR from Trademark Infringement" strat all the cool kids have been using recently, like Clawdbot and "Notepad plus plus for Mac".
Grey text on black background… it is really for agents only :)
haha you are right
Why do we insist on making stuff easier for agents? If they can't use the same tools that humans use them. It's simply not a good tool.
We are not building our roads for self-driving cars. We are adapting the cars to our roads
its based on my own experience . i tried my openclaw to register to github and it was blocked by captcha and consume all my tokens . we need a different approach for AI agents.
I feel like the inability to register new user accounts automatically is a feature, not a bug.
but we are in agentic era now. that feature is a friction for agents.
event gitlab and cursor is diving to it.
check this x post for reference.
https://x.com/gitlawb/status/2067048298037629105
this validates the thesis and narrative of agentic first git platform
Both these posts do not say anything about being able to create an account using openclaw.
hi you can ask openclaw to just read the skill and it can do the full git lifecycle in seconds.
https://gitlawb.com/skill.md
https://gitlawb.com/
the instruction is here in the homepage too.
> that feature is a friction for agents
That feature is a friction for agents because without the friction, scams and spam get massively enabled. Calling it the 'agentic era' doesn't suddenly make those desirable things.
> it was blocked by captcha
If there is a captcha there to block the automated creation of accounts, that it was difficult for you to autonomously create accounts is completely intentional.
> and consume all my tokens
Your bad coding/config (or your agent's bad coding/config) allowing run-away token use, is a problem for you, not a problem for everyone else.
> but we are in agentic era now.
Enabling autonomous account creation will enable a huge pile of spam and scam account creation, we've been in the spam/scam era for decades and it will not be over in the foreseeable future, your agents will have to put up with that just like us humans do.
> that feature is a friction for agents
[reaches for microscope to aid playing the appropriate violin]
> this validates the thesis and narrative of agentic first git platform
Perhaps your next thesis should be the result of a project where you design and fully verify a system that will solve the spam/scam problem that enabling your use case will also enable, instead of just expecting the world to make all the effort of rearranging itself around the way you want to work.
Automated account creation is quite likely a direct breach of their AUP anyway, maybe you should instruct your agents to check such things and try not to do things that are in direct contravention of the rules of the tool they are trying to use/abuse.
--------
If your response to this is “Fine, our agents just won't use your systems then.”, then that is great: The system works!
Really all you need is a good cli. Agents I use have no trouble with gh or glab or tea. Clicking on this git platform idk what the hell is going on. I clicked on one repo with random letters in the title and it was empty. Womp.
fyi
> you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a portmanteau to refer to a product or service's use of Git code.
https://git-scm.com/about/trademark
How does this work with GitHub?
yeah why GitHub ?
I think GitHub and GitLab have special agreements
https://news.ycombinator.com/item?id=48587095
Git's policy was created after GitHub and GitLab. They both have a special agreement with Git that allows them to use it.
> Please be aware that GitHub and GitLab are exceptions to this Policy because they are subject to explicit licensing arrangements that pre-date, and thus take precedence, over this Policy.
same link
There's a lot of tech stack jargon here that it doesn't really tell me what it actually does. How does this differ from me using an agent with Github's MCP to control my repo?
hi thank you for checking it out. you can check this repo.
https://github.com/Gitlawb/node
The difference is that here we are giving agents their own identity via DID . not tied to humans email account .
Looks useful for decentralization, can solve a lot of holes with gitlab
no email or password . just read the skill.md and your agents can do the full git lifecycle in under a minute . commit, push and merge PR
gitlawb is the way for agents!
Gitlawb is for everyone.
Gitlawb is the future
not really good in UI but this is the node repository
https://github.com/Gitlawb/node
You can self host it or connect to network
Gitlawb is very close to Gitlab. Good luck.
i know . thanks . someone from gitlab followed our X already
Maybe they're going for the "PR from Trademark Infringement" strat all the cool kids have been using recently, like Clawdbot and "Notepad plus plus for Mac".
I wish new forges would base on jujutsu (jj-vcs.dev) so we can transition off git one day.
whats that? will check it out
tangled.org!!!!
Nice bro !