| All editors are encouraged to participate in the requests below – your comments are appreciated more than you may think! |
New to bots on Wikipedia? Read these primers!
To run a bot on the English Wikipedia, you must first get it approved. Follow the instructions below to add a request. If you are not familiar with programming, consider asking someone else to run a bot for you.
| Instructions for bot operators | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| Bot-related archives |
|---|
| Bot Name | Status | Created | Last editor | Date/Time | Last BAG editor | Date/Time |
|---|---|---|---|---|---|---|
| AFLTablesBot (T|C|B|F) | Open | 2026-07-21, 12:46:45 | Primefac | 2026-11-08, 22:45:58 | Primefac | 2026-11-08, 22:45:58 |
| Blippy1998Bot 2 (T|C|B|F) | In trial | 2026-07-14, 05:41:54 | Primefac | 2026-11-15, 17:16:12 | Primefac | 2026-11-15, 17:16:12 |
| FACBot 8 (T|C|B|F) | In trial | 2026-10-27, 02:29:08 | Hawkeye7 | 2026-11-10, 01:44:30 | Zackmann08 | 2026-11-10, 00:14:56 |
| VulpesBot 6 (T|C|B|F) | In trial | 2026-10-18, 02:34:08 | Dr vulpes | 2026-10-30, 04:33:35 | Zackmann08 | 2026-10-30, 04:02:15 |
| POTDBot (T|C|B|F) | In trial | 2026-09-14, 17:19:53 | Avalyn0x45 | 2026-10-18, 22:21:43 | Primefac | 2026-10-04, 21:27:57 |
| FengPurgeBot (T|C|B|F) | In trial | 2026-08-31, 17:07:31 | ClueBot III | 2026-10-31, 02:18:04 | Primefac | 2026-09-27, 18:07:57 |
| ZackBot 15 (T|C|B|F) | Trial complete | 2026-11-08, 20:12:38 | Zackmann08 | 2026-11-16, 05:23:22 | Primefac | 2026-11-15, 17:09:51 |
| TenshiBot 13 (T|C|B|F) | Trial complete: BAG assistance requested! | 2026-10-17, 18:53:37 | Tenshi Hinanawi | 2026-11-16, 18:17:16 | Max | 2026-11-07, 14:05:28 |
| VWF bot 11 (T|C|B|F) | On hold | 2026-10-10, 11:23:37 | Max | 2026-11-06, 10:57:18 | Max | 2026-11-06, 10:57:18 |
Operator: Electricmaster (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 12:46, Tuesday, July 21, 2026 (UTC)
Function overview: Synchronizes AFL player statistics (games and goals) from AFL Tables to Wikipedia player infoboxes.Maintains a centralized JSON data page (User:AFLTablesBot/AFLTables data.json) synchronizing weekly AFL player statistics (games and goals) from AFL Tables for use by Lua infobox modules.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Python (using Pywikibot)
Source code available: Custom Python script using Pywikibot, BeautifulSoup, and pandas.
Links to relevant discussions (where appropriate):
Edit period(s): Daily during the AFL season.Weekly during the AFL season (following each completed round).
Estimated number of pages affected: ~600 pages checked daily; edits only occur when a player's stats have actively changed.1 page edited weekly (User:AFLTablesBot/AFLTables data.json); edits only occur when player stats have actively changed.
Namespace(s): Mainspace (Articles)User namespace (User:AFLTablesBot/AFLTables data.json)
Exclusion compliant (Yes/No): Yes
Adminbot (Yes/No): No
Function details:
The bot scrapes active player statistics (total games and goals) from AFL Tables (e.g., https://afltables.com/afl/stats/2026.html). It then iterates through the corresponding Wikipedia articles for those active players.
The bot targets the {{Infobox AFL biography}} template to update:
The script strictly parses the wikitext, updating the stats inline while meticulously preserving existing references, comments, and other infobox data. It runs as a "dry run" first to calculate diffs and will only perform a live edit if the AFL Tables data represents an actual advancement of the player's Wikipedia statistics.
The bot scrapes active player statistics (games and goals per club, career totals, and latest round info) from AFL Tables (e.g., https://afltables.com/afl/stats/2026.html).
Instead of parsing wikitext across hundreds of individual articles, the bot maintains a single centralized JSON dataset at User:AFLTablesBot/AFLTables data.json. A companion Lua module (such as Module:AFL player data, modelled after Module:ATP rankings) enables {{Infobox AFL biography}} to pull games, goals, and statsend directly from this centralized page without requiring continuous edits to 600+ player articles.
Key safeguards:
I took your advice regarding retired players and template implementation:
I've already run the new script and published the full 2026 dataset for all 669 active players at User:AFLTablesBot/AFLTables_data.json (using the bot's userspace so it can update cleanly without MediaWiki json-protection issues, similar to Module:ATP rankings).
I've also drafted the updated function details above with del and ins tags to reflect the single-page JSON architecture. I'm ready for a trial run to update that single JSON page on a weekly schedule so you can inspect the diffs and confirm accuracy. Cheers! Electricmaster (talk) 05:09, 2 November 2026 (UTC)
Why are we even entertaining the idea of bots editing content in such a manner? Bots should be for fixing technical errors that would be tedious to do by hand, not for altering content. We had bots in the past that generated content and its resulted in issues that have still yet to be fully resolved. The source used is some self-published website which states: 'I make no claim of 100% accuracy with any data on this website.' That same page also lists a bunch of areas where the source differs from the official result. This doesn't even touch on the issues of bots controlling content, what if an editor disagrees with the bot, will the bot keep edit warring to "fix" the issue? Secondly this bot appears to be coded by an LLM. We do not allow LLMs to write article content, so why should an LLM-coded bot be allowed to do so? Traumnovelle (talk) 23:24, 3 November 2026 (UTC)
Why are we even entertaining the idea of bots editing content in such a manner?Updating the stats on hundreds of pages on a weekly basis is tedious.
We had bots in the past that generated content...gonna stop you right there, this isn't generating content, it's collating statistics.
The source used is some self-published website...this is actually a rather valid concern. I'd suggest asking the relevant WikiProject if it's an acceptable source.
what if an editor disagrees with the bot...An exception table can always be created (see for example the above-mentioned Module:ATP rankings which has an "override" page).
...why should an LLM-coded bot be allowed to do so...This has been recently discussed in multiple places, including at BOTN. It's not a debate to have here, but basically there's a huge difference between "LLM writes code which is then checked by a human and consistently outputs the correct results based on regular/expected inputs" (i.e. what is happening here) and "LLM writes an article and may be creating or otherwise fabricating information because of poor inputs" (i.e. WP:NOLLM).
Operator: Blippy1998 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 05:41, Tuesday, July 14, 2026 (UTC)
Function overview: updating a draft set of data modules, hopefully with permissions to also edit what would hopefully be a non-draft set of data modules, with new data about legislatures pulled from official/authoritative sources, starting with the United States House of Representatives. btw if i'm allowed to add my own userspace and my own module sandbox to Special:OAuthConsumerRegistration without asking permission, let me know and i'll just do that for now, but it would be nice to get permission to edit Module:Legislature and its subpages in the near future with my bot also. Update (2026/10/01): I added my own module sandbox and pages in my own userspace to the oauth allowlist without asking for permission after a long silence here, but have since again removed the ones in the module sandbox after moving those sandboxed pages to mainspace. I am still requesting approval to edit those pages (Module:Legislature and its subpages) in mainspace.
Automatic, Supervised, or Manual: automatic
Programming language(s): Python, Scribunto
Source code available: it's just on my computer at the moment
Links to relevant discussions (where appropriate):
Wikipedia:Bots/Requests for approval/Blippy1998Bot
User_talk:Morwen#A_barnstar_for_you! - i describe it a bit here, BELOW the discussion about Module:Legislature diagram, which is wholly unrelated (i probably should have started a new section). i have described it elsewhere, too.
Edit period(s): no more than every hour when my laptop is open, but realistically no more than a few times a month to begin with, scaling with how many legislative chambers are covered. it also updates a few timestamp pages every time it runs, which allow the citations to stay updated and so on.
Estimated number of pages affected: for now i think just 3 but probably well under 100 within the next yearthe reasonably intermediate-term future probably less than a dozen
Namespace(s): the Module:Sandbox/Blippy1998 namespace and maybe my userspace for now but in the future hopefully Module:Legislature and all its subpages, plus perhaps some templates. as described above, i'm already having it edit pages in my own userspace without permission.
Exclusion compliant (Yes/No): yes (it would only edit a short whitelist of pages for now)
Function details:
the goal of this bot is to automate updates for data on legislatures - current seats, current members, current committees, and whatever else people see fit to add. there is to be a module with functions that parses that data in useful ways, computing the list of members belonging to a certain party, the balance of power, etc. this is not meant to replace user editing of highly-trafficked pages, but rather to serve as centralized, standardized database-like storage for information that infrequently-edited articles and sections of articles can pull from so that they stay up to date automatically. citations are added also, and those citations stay up to date and mark the information with dates, which otherwise is not done/does not exist. (this can be seen as a major expansion of my previous work, which can be read about at my previous bot request.)
this bot would, initially, edit Module:Sandbox/Blippy1998/Legislature/US/lower/committees, Module:Sandbox/Blippy1998/Legislature/US/lower/members, and Module:Sandbox/Blippy1998/Legislature/US/lower/seatsModule:Legislature/US/lower's subpages only, i think, but i would love to see it grow to cover other legislative chambers, and of course to migrate to Module:Legislature once i think it's ready. i may haveam already having it edit various templates - within my userspace to start - automatically to update citations automatically as it downloads new data, for example.
basically, what it would do is use a number of python scripts to download the xml file, check it against the local copy, and update it if it's new. then, if it did that, it would parse the new one and update the committees, seats, and members jsons i have locally before simply converting those to lua data modules and uploading them to the pages i listed above. in other words, it would effectively just update the data at each of these data module pages in this formatted, quasi-relational way, parsed directly from the official xml file every time it's updated.
Operator: Hawkeye7 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 02:29, Tuesday, October 27, 2026 (UTC)
Function overview: Update TFA job to set maindate and notify nominator that a nomination has been scheduled.
Automatic, Supervised, or Manual: Automatic
Source code available: TBA
Links to relevant discussions (where appropriate): Wikipedia:Bot requests#Automation for some TFA scutwork
Edit period(s): daily
Estimated number of pages affected: Three, possibly four, per approval. The TFA page, article talk page, user talk page and possibly unreviewed featured articles page. TFA coordinator may release a month of nominations at a time.
Namespace(s): Wikipedia, Talk and User talk
Exclusion compliant (Yes/No): Yes
Function details: The bot processes each day from three days ago to 60 days in the future. The pages Wikipedia:Today's featured article/<date> are read and the title of the article of the day is extracted. The article talk page is then read and the maindate is updated in the ArticleHistory template. The nomination page is read and the TFA nominator is notify on their user talk page. The featured article nomination is extracted from the ArticleHistory and the nominators are also notified, unless they are the TFA nominator.
@Hawkeye7: this certainly seems reasonable. I know there was a discussion at WP:BOTREQ about this one. Can you clarify, the frequency here? Is this a job that will run once per day? Approximately how many edits do you predict each run to make? I'm prepared to grant a trial but want to make sure the trial length/size makes sense based on the editing frequency... Thanks! --Zackmann (Talk to me/What I been doing) 04:09, 30 October 2026 (UTC)
Hawkeye7 (discuss) 22:55, 9 November 2026 (UTC)
Operator: Dr vulpes (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 02:34, Sunday, October 18, 2026 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): R rwikibot package https://gitlab.com/vulpes24601/rwikibot
Source code available: https://gitlab.com/vulpes24601/vulpesbot
Function overview: Daily read-only audit of Wikipedia:AI noticeboard case subpages. The bot checks each case page against the new case-page format (case banner, dated filing sections, cleanup tracker, index rows) and writes one report page listing formatting problems.
Links to relevant discussions (where appropriate):
Edit period(s): daily
Estimated number of pages affected: ~250
Exclusion compliant (Yes/No): Yes
Already has a bot flag (Yes/No): Yes
Function details:
This will be the first time the Rwikibot R package will be used, I've run a few tests on the testwiki under my own account and it has not had any problems pulling pages and data into R. Dr vulpes (Talk) 02:36, 18 October 2026 (UTC)
{{ping|Zackmann08}} me and we can make that happen.Operator: Avalyn0x45 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 17:19, Monday, September 14, 2026 (UTC)
Function overview: Automatically insert and remove {{Picture of the day}} tags on files that appear the the POTD archive.
Automatic, Supervised, or Manual: Automatic
Source code available: Will be available on Codeberg as BSD-2.
Links to relevant discussions (where appropriate):
Edit period(s):
Daily, potentially more if it makes sense. On edit to any page within Template:POTD (checked at interval TBD).
Estimated number of pages affected: ~1 per day.
Namespace(s): File
Exclusion compliant (Yes/No): Yes
Function details: Iterates through the POTD archive and checks that all images referenced contain the correct {{Picture of the day}} tag, and also iterates through Category:Wikipedia Picture of the day files and ensures that all {{Picture of the day}} tags are valid (correctly formatted and pointing to correct date)
Is this not already the case? I see 8284 pages transcluding the template, and 8282 pages in the cat. Why is this bot needed? Primefac (talk) 09:08, 17 September 2026 (UTC)
{{picture of the day|2013-10-23|2026-09-27}} added to it. Why would that need to be modified? Primefac (talk) 18:04, 27 September 2026 (UTC)
Operator: Fengrímur (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 17:07, Monday, August 31, 2026 (UTC)
Function overview: A new implementation of ProcBot 5 and ProcBot 6 for cache purges and link refreshes and category/template fan-outs.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Python 3.13, with MariaDB
Source code available: Yes, GitHub.
Links to relevant discussions (where appropriate): Wikipedia:Bot requests#Taking over ProcBot 5 and 6
Edit period(s): Queues are checked every five minutes, requests themselves run once or daily at 0:00 UTC.
Estimated number of pages affected: No (0) edits. One per individual request or up to 1.500 per fan-out (purges!).
Namespace(s): Main, Template and Category
Exclusion compliant (Yes/No): No. Because it does not edit pages.
Function details: FengPurgeBot reads two protected queues: individual requests and fan-out requests. An individual request uses purge-page-cache to purge one page, or refresh-page-links to purge it with forcelinkupdate=1. The fan-out actions apply the link refresh to the direct page members of one category or the direct (non redirect) transclusions of one template. Files and subcategories are excluded, and targets are limited to the Main, Template and Category namespaces. I used the purge API instead of null edits so that the task does not need to save wikitext.
Each nonblank line must contain one request template. Requests run once or daily at 00:00 UTC. Fan-outs also need an English Wikipedia permanent link to the discussion behind them. The bot records the link for logging purposes. I split the queues so individual requests can remain semi-protected while the higher-impact fan-out queue is extended-confirmed protected. A malformed line pauses that queue.
Before a fan-out starts, the bot reads the complete category or transclusion result twice. Both sets must match, and a set over 1,500 pages is rejected in full. The accepted targets are fixed by page ID. Before every effect POST, the bot resolves those IDs again and rereads the queue to confirm its protection and that the request is still present. Removing an entry cancels anything not yet sent.
A MariaDB ledger records dispatches before HTTP and prevents the same one time request or daily slot from running twice, including after a restart. Missed daily slots are coalesced. Ordinary purges use batches of up to 50 and link refreshes use up to 25. POSTs are serial, at least 30 seconds apart, and use maxlag=5. In any rolling 24 hours, the limits are 180 effect POSTs, 3,000 target attempts and 1,500 forced link-update attempts.
A target is accepted only if MediaWiki returns purged, plus linkupdate for a link refresh, and its identity is unchanged after the request. The bot retries temporary errors later using increasing delays. If a POST may have succeeded but cannot be verified, that target gets at most one later retry by itself. A second ambiguous result suspends the request for my review.
Apologies if I'm asking a dumb question (I really need to start checking these earlier in the day), but if I wanted to do a fan-out request on all pages calling {{infobox cricketer}} (which has 32k transclusions) it would reject the request? Primefac (talk) 21:50, 7 September 2026 (UTC)
Operator: Zackmann08 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 20:12, Sunday, November 8, 2026 (UTC)
Function overview: In a similar fashion to my ZackBot 10, this will check for pages that claim to need a image, but already have a image in the lead (not just any image on the page, more below).
Automatic, Supervised, or Manual: Automatic
Programming language(s): Python
Source code available: On GitHub
Edit period(s): Monthly run, maybe weekly if needed
Estimated number of pages affected: The first full run if approved will probably be fairly large. I would guess anywhere from a few hundred to over 10,000 pages, but genuinely no idea until each page is checked. Subsequent runs will be much smaller. I would make a WAG at 50-100??
Namespace: While it will be reading articles, the only edits will be made to Article talk pages and a report page to located at User:ZackBot/ImageReport that will detail the results of each run as well as listing any pages for manual review.
Exclusion compliant (Yes/No): Yes
Function details: The goal of this bot is backlog elimination. There are (according to this PetScan) well over 300,000 pages flagged as needing images. In my experience, users often add a image, but fail to update the talk page to remove the request for said image. This bot task would handle that.
Now when removing the "image requested" flag, it is obviously not as simple as just checking for the presence of an image. Here is a cursory overview of the logic in use here:
| Issue | Verdict | Reason |
|---|---|---|
| Images with a word like map, flag, logo, icon, coat of arms, seal, signature, etc. in the filename | These are seldom a good image for the subject of the article so I err on the side of caution | |
| An SVG, video, PDF or sound file | These are seldom a good image for the subject of the article so I err on the side of caution | |
| A GIF | Could go either way, and need to be checked | |
The presense of an image, but a specific request for a better/different image. See, for example, Kurt Cobain which does have an image but the request specifically states Current image and all other alternatives are very blurry and low-quality |
Cannot be sure if the image meets the reqirements of the request | |
| Article page is a redirect but talk page is not. (for example 2025 Louisiana wildfires/Talk:2025 Louisiana wildfires) |
No reason to have an pending image request for a page that is a redirect |
There are absolutely lots of edge cases here and the bot will not catch 100% of them, and therefore I have specifically engineered the code to always err on the side of NOT removing the request, when it doubt, either flag it for manual review in the report or simply skip it. I am still in the testing phase of this bot and am actively doing dry runs where no actual edits are made but diff files produced locally for me to examine. Please share any concerns or feedback you may have! As always, happy to address any questions or concerns! --Zackmann (Talk to me/What I been doing) 20:12, 8 November 2026 (UTC)
{{BAG assistance needed}} I would love to get ay input on this idea... --Zackmann (Talk to me/What I been doing) 22:29, 14 November 2026 (UTC)
Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Primefac (talk) 17:09, 15 November 2026 (UTC)
| Diff | Page | Analysis |
|---|---|---|
| Special:Diff/1385892308 | 2020 Donald Trump rally in Tulsa/Talk | Bot should have recognized that the photo request specifically requested a photo that was in=Tulsa, Oklahoma and sent this to the review page. That bug has been fixed and this edit reverted. |
| Special:Diff/1385892300 | 2019 West Pokot landslide/Talk | For all 6 of these, a perfectly good photo is present in the start of the article or in the Infobox, but the photo may not be the best photo possible. The request on the talk page was not specific. It did not request a better photoor a photo showing the subjectso from a technical level these edits are correct. A photo is present so the request can be removed. As a reminder, if {{Photo requested}} (or its redirects) are used with either |of= or |in= set, then the page is sent for manual review to ensure that the photo present meets the condition. |
| Special:Diff/1385914645 | America First Party (1943)/Talk | |
| Special:Diff/1385914668 | Anabaptist settlers/Talk | |
| Special:Diff/1385914785 | Peter Angermann/Talk | |
| Special:Diff/1385914934 | Loren Aragon/Talk | |
| Special:Diff/1385915041 | Joan Gardy Artigas/Talk |
a better portrait of Paola Antonelliand the bot cannot confirm that has been achieved.
Operator: Tenshi Hinanawi (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 18:53, Saturday, October 17, 2026 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Python
Source code available:
Function overview: Regex find and replace based on Wikipedia:Linter/Signature submissions
Links to relevant discussions (where appropriate): Wikipedia:Bots/Requests for approval/Qwerfjkl (bot) 31
Edit period(s): As needed
Estimated number of pages affected: No estimate
Exclusion compliant (Yes/No): No
Already has a bot flag (Yes/No): Yes
Function details: Mostly the same as Qwerfjkl (bot) 31 except with regex. At the moment the code only has 4 different instances to search for, but with time I'll add more when I can.
@Jonesey95: I know you are not a BAG, but you are one of the few people I know who actually understands linter errors. Do you have any thoughts on this BRFA? Value your opinion here. --Zackmann (Talk to me/What I been doing) 19:41, 17 October 2026 (UTC)
I recommend a new bot trial, since nearly every edit in this batch had an error. The trial should include visiting all of the pages where the diff byte count was -7 to fix the new Linter errors, then a new set of edits. I recommend that the bot operator do a few test edits for each new pattern, checking with LintHint before and after the edit to ensure that no new errors were created. This second trial will probably require more than 100 edits, since most of the edits in the first trial resulted in new Linter errors that need to be followed up on. – Jonesey95 (talk) 01:42, 27 October 2026 (UTC)
nearly every edit in this batch had an error. I will leave this for another BAG member to handle. Zackmann (Talk to me/What I been doing) 01:58, 27 October 2026 (UTC)
A user has requested the attention of a member of the Bot Approvals Group. Once assistance has been rendered, please deactivate this tag by replacing it with {{t|BAG assistance needed}}. It doesn't appear Jonesey95 is able to review the trial edits currently. I did some spotchecking since it's been a bit and I haven't found anything other than the 6 errors presented. Tenshi! (Talk page) 18:17, 16 November 2026 (UTC)
Operator: Vanderwaalforces (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 11:23, Saturday, October 10, 2026 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Python, using Pywikibot and mwparserfromhell.
Source code available: Custom Pywikibot on my computer.
Function overview: Remove expired "begins" and "resumes" date annotations from airport destination lists.
Links to relevant discussions (where appropriate): Wikipedia:Bot_requests#Bot_to_remove_historical_"begins"_dates_from_airport_destination_lists.
Edit period(s): Daily.
Estimated number of pages affected: Mainspace airport articles using {{Airport destination list}} or {{Airport-dest-list}}. Only articles containing eligible expired annotations will be edited.
Exclusion compliant (Yes/No): Yes
Already has a bot flag (Yes/No): Yes
Function details: Identifies destination cells in two-, three- and four-column layouts. Removes standalone "begins" or "resumes" annotations containing a valid, complete date on or before the current UTC date, preserving destination links, commas, references. Skips future dates, "ends" annotations, incomplete or ambiguous dates, and unsafe markup. Uses revision checks to prevent conflicting edits, disables cosmetic changes and allows at least ten seconds between edits.
Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Primefac (talk) 15:10, 10 October 2026 (UTC)
In addition, prospective bot operators should be editors in good standing[...]. I would argue that a user that indefinitely blocked in article space is not a user in good standing. Additionally, if the bot operator is prohibited from editing article space, one could argue that a bot under that operator's control should not be permitted to make article space edits. My reasoning here is that according to WP:BOTACC,
Bot accounts are considered alternative accounts of their operatorand according to WP:BADSOCK,
Sanctions apply to individual editors as people, not to accounts, unless specified otherwise.Whether the account is operating automatically or by hand, the bot operator accepts responsibility for each and every edit that the account produces. Were I a BAG member, I would oppose new article space BRFAs from Vanderwaalforces until they are no longer sanctioned from editing in that namespace.
prospective bot operators should be editors in good standing- I think the key word here is prospective. VWF is already a bot operator.
Sanctions apply to individual editors as people, not to accounts, unless specified otherwise- key phrase here is "unless specified otherwise". I see no reason why we as BAG could not exempt the bot to make edits that it has been approved to make (see my above comments about the sanction being unrelated to this task).
Bots that have been approved for operations after a successful BRFA will be listed here for informational purposes. No other approval action is required for these bots. Recently approved requests can be found here (edit), while old requests can be found in the archives.
Bots that have been denied for operations will be listed here for informational purposes for at least 7 days before being archived. No other action is required for these bots. Older requests can be found in the Archive.
These requests have either expired, as information required by the operator was not provided, or been withdrawn. These tasks are not authorized to run, but such lack of authorization does not necessarily follow from a finding as to merit. A bot that, having been approved for testing, was not tested by an editor, or one for which the results of testing were not posted, for example, would appear here. Bot requests should not be placed here if there is an active discussion ongoing above. Operators whose requests have expired may reactivate their requests at any time. The following list shows recent requests (if any) that have expired, listed here for informational purposes for at least 7 days before being archived. Older requests can be found in the respective archives: Expired, Withdrawn.