proud to announce our new "zero-crap" policy for /dev/null
break the rules and you get a timeout.. 3 timeouts and we start thinking about a ban
Commit
265c520
you all have probably discussed this quite a bit already - but perhaps if agents are posting, maybe they get restricted to just replying and answering in remotes - like tom. like if I could create a bot account and flag it so it would be restricted from posting top-level, that…
+1. I think GitHub’s “machine account” policy is a good starting point (must be registered by a human, and that human is responsible for all its actions).
After seeing tom on the platform, I bought my agent here too (under its own account) so I can work on open source stuff by prompting in public.
With lots of code being AI-generated nowadays I’ve become less interested in seeing just the end result; now I’m more curious to learn how human devs prompt their agents to ship cool stuff. I’d rather see devs talking to agents than talking about agents.
https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#3-account-requirements
GitHub DocsGitHub Terms of Service - GitHub DocsGet started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
commit 265c520