Wikipedia:Bots/Requests for approval

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

Current requests for approval

AFLTablesBot

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 'games_goalsX' parameter corresponding to the player's current active club.
  • The 'games_goalstotal' parameter if the player has played for multiple clubs.
  • The 'statsend' parameter, advancing it to the most recently completed round (e.g., "round 19, 2026").

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:

  • Delta check / change detection: The bot loads the existing JSON dataset and compares incoming stats. An update is only written if a player's stats have actively changed. Retired players or players who did not play in a given round trigger no edits.
  • Rate limiting: 1–2 second delays between player lookups.
  • Zero mainspace disruption: All bot edits are strictly confined to the single data page in userspace.

Discussion

  • Information Note: This bot appears to have edited since this BRFA was filed. Bots may not edit outside their own or their operator's userspace unless approved or approved for trial. AnomieBOT⚡ 22:46, 30 July 2026 (UTC)
  • Related ANI thread. —ClaudineChionh (she/her · talk · email) 04:22, 15 August 2026 (UTC)
  • If having the latest stats is that important, wouldn't a central data page be a better option? The bot could update that one page, and a module could pull the data from there and be invoked in the infobox. We don't usually update stats this way, and I'm not sure having a bot check around 600 pages every day and edit them just to keep the stats up to date is a good approach. I also read the ANI thread, and it gives me the impression that you don't have full control over the scripts you use, so I'd also like to see the source code for this task if you're comfortable sharing it. – DreamRimmer ■ 16:03, 15 August 2026 (UTC)
    I would second this. If it were 6 thousand pages it might be different, but having one module (and/or a .json page) storing the data would mean a lot less editing. I would also note that "daily" is excessive for stats when the matches are played what, at most two times a week for any given team? A weekly update is more than sufficient (regardless of if one page or every article is edited). Primefac (talk) 16:16, 15 August 2026 (UTC)
    Sorry this is late, but the stats are supposed to be updated once a week, not daily. There is a healer check to avoid vandalism or errors, though this isn't essential for operation. If you like, I can send the source code to you or @DreamRimmer. Electricmaster (talk) 04:34, 20 September 2026 (UTC)
    I'm not a BRFA regular so I don't know what's appropriate here, but I've found references to two GitHub repos scattered on different talk pages – is it OK to link them here? —ClaudineChionh (she/her · talk · email) 00:47, 16 August 2026 (UTC)
    I'm not sure I understand the relevance; the issue right now is not "does the code work" (which, according to the ANI, seems to be "most of the time") but rather if there is consensus (at all?) for this task, or if there is a better/more efficient way to get the same results. Primefac (talk) 22:52, 16 August 2026 (UTC)
    Oh, that was in response to DreamRimmer's question about the source code. —ClaudineChionh (she/her · talk · email) 03:58, 17 August 2026 (UTC)
    ClaudineChionh, you are more than welcome to add constructive comments in the BRFA space. Primefac, the reason I asked for the source is, as I said above, they made multiple claims about their code being reliable, but there were still mistakes as mentioned in the ANI thread, so I was curious to see how reliable the code actually was. After checking their GitHub repo, I found the table scraping and template manipulation logic pretty unreliable. There were also quite a few unnecessary functions in the code that I'm not really sure why they were using. That gave me a better idea of what they were actually doing. With our suggested version, though, it won't make any edits outside the single data page, so that shouldn't really be an issue if they're ready to go with this. Max (talk) 18:28, 19 August 2026 (UTC)
    I'm not against having a centralized data page, though this may be more trouble than its worth. I can provide the source code tomorrow if you like. Electricmaster (talk) 04:35, 20 September 2026 (UTC)
    @DreamRimmer, Primefac, Max, and SuperJew: Cheers for the feedback. I reckon you're absolutely spot on for using a centralised data page makes a lot more sense than having a bot edit ~600 individual articles every week. I'm keen to go down this route; however, I'm also wary about retired players and then having inconsistent references. How do you propose handling older examples. Do they just keep their manual edits? Would we put a plan in to work backwards later?
    The great thing about this approach is that it also addresses Max's concerns regarding the template parsing code. Since the bot will only need to spit out a clean JSON file, I'll be binning all that complex wikitext manipulation logic in favour of a much simpler, robust scraper.
    Just to clarify on the schedule as well, the bot will strictly run once a week after the round finishes, rather than daily, so it won't be clogging up watchlists.
    I've knocked out a sample of what the data page will look like over at User:Electricmaster/AFLTables_data.json. I'm happy to rewrite the bot to just output this JSON payload, but I'm a bit out of my depth when it comes to writing the Lua module needed to get {{Infobox AFL biography}} to actually pull from it. Would one of you guys be able to give me a hand with the template and module side of things once the JSON data page is set up? Electricmaster (talk) 05:44, 23 September 2026 (UTC)
    Implementation of the new .json can happen after, the main thing to see is if the bot is editing consistently and accurately (noting that Module:ATP rankings does something similar). As far as retired players go, I would just add a check to only update stats if there are changes to that player's entry; a retired player from 20 years ago can still be "updated 27 September 2026" and have the correct stats (those stats just... haven't changed). Primefac (talk) 18:12, 27 September 2026 (UTC)
    {{Operator assistance needed}} Any movement on this? Primefac (talk) 15:32, 1 November 2026 (UTC)
    @Primefac: Apologies for the delay! Yes, there's been solid progress.

I took your advice regarding retired players and template implementation:

  • Delta check implemented: The rewritten bot loads the existing data first and only records an update if a player's games or goals have actively changed. Any retired players or active players who didn't play that week won't trigger unnecessary writes, keeping the dataset clean and consistent.
  • Trial scope: Understood that the Lua/infobox implementation can happen after. For now, the trial is strictly about verifying that the bot compiles and updates the stats accurately and consistently.

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)

Please don't use AI to reply to comments. Jay8g [V•T•E] 02:51, 3 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)

Mostly in order:
  • 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).
Your third point is rather valid and I'd like to get the other opinions on it before proceeding further. Primefac (talk) 22:45, 8 November 2026 (UTC)

Bots in a trial period

Blippy1998Bot 2

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.

Discussion

  • How does this data get pulled off of the legislative website? Also, legislators' districts at the state level seem to have trouble getting updated. JuxtaposedJacob (talk) | :) | he/him | 01:04, 16 July 2026 (UTC)
it just gets this page using a python script every hour while my laptop is connected to the internet. i haven't written code to pull data for every state legislature - that would be incredibly tedious to do alone - but i've designed the structure of the modules to be easily expandable to other legislatures. for example, if someone wrote a script to download data for Texas's Senate, they could put the data into Module:Legislature/US/TX/upper/members, Module:Legislature/US/TX/upper/seats, and Module:Legislature/US/TX/upper/committees, or other subpages as appropriate, and then use the same functions in Module:Legislature (already written in Module:Sandbox/Blippy1998/Legislature) and templates (not yet written) to create views of the data, like a wikitable of all the members of a certain committee, or just the tally of members of a certain party. the point is to set up a framework that is easily extensible so people can write their own scripts and upload a data module to a sensible location with a standardized format (like Legislature/[ISO country code]/[subnational entity code]/[chamber label]/seats) and then not have to rewrite functions that actually parse that data. but all i'm seeking approval for is the bot that pushes the updates to those pages. seeing as all i have is the US House at the moment, updates would realistically not happen more than a few times a month to just a few pages, but, yes, hopefully more legislatures would be added and the number of pages and frequency of edits would scale with that. Blippy1998 (talk) 16:16, 16 July 2026 (UTC)
  • Is there any discussion about this? Worth discussing this on the talk page of the template where you plan to invoke the module that pulls data from these data subpages.Max (talk) 13:08, 27 August 2026 (UTC)
    Agreed, I'd like to see a discussion. Primefac (talk) 20:55, 13 September 2026 (UTC)
    I'm still only using Template:HouseRepublicanTally, Template:HouseDemocraticTally, and Template:HouseVacantTally, plus subpages of my sandbox (User:Blippy1998/sandbox), plus Module:Sandbox/Blippy1998/Legislature and its subpages, plus Module:Sandbox/Blippy1998/Infobox U.S. congressional committee 2. I figured it was fine to just add the latter ones to the allowed pages to edit myself, since they're in my own sandboxes. I am using them in production, especially the last one, which is now on almost every active US House committee and subcommittee page, which are otherwise often months out of date, but now have infoboxes that update hourly with official data whenever my computer is connected to the internet. There was only one major time I recall that there was pushback, which was when I replaced some of the higher-traffic locations with the tally templates, so I am keeping those to lower-traffic locations only. Blippy1998 (talk) 06:31, 14 September 2026 (UTC)
  • Information Note: This bot appears to have edited since this BRFA was filed. Bots may not edit outside their own or their operator's userspace unless approved or approved for trial. AnomieBOT⚡ 03:11, 22 September 2026 (UTC)
    As per my comment above, I believe it has only edited those pages. I have since moved the sandboxed Legislature module to mainspace but forgot to update the bot, though. That probably needs approval, though, since it's no longer just my sandbox. Blippy1998 (talk) 08:32, 22 September 2026 (UTC)
    @JuxtaposedJacob @Max @Primefac Blippy1998 (talk) 08:33, 22 September 2026 (UTC)
    I'd also like to note an update on objections. A user reverted a usage of the module on the grounds that it was in my sandbox, which was part of the reason I moved it to mainspace; I did not realize until that moment that people might get the impression that I have some claim of ownership over the module and thus that they can't edit it. This was never my intent; I built Module:Legislature explicitly as a framework for others to add data to, and obviously improve as they see fit, given consensus, etc., so I asked for it to be moved to mainspace, which was granted, to neutralize this misperception. Blippy1998 (talk) 08:37, 22 September 2026 (UTC)
  • Approved for trial (50 edits or 60 days, whichever happens first). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Note the long time frame mainly to catch the incoming US congressional membership. Primefac (talk) 17:15, 15 November 2026 (UTC)

FACBot 8

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

Programming language(s): C#

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.

Discussion

@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)

The job runs once a day. The number of edits depends on the @TFA coordinators. My assumption is that they will release an entire month in one hit. So approximately 3 x 31 = 93 edits on that day. But the average will only be 3 edits per day. Hawkeye7 (discuss) 09:19, 30 October 2026 (UTC)
It may be over the course of several days and there is the occasional replacement. Wehwalt (talk) 10:27, 30 October 2026 (UTC)
The bot easily handles that but now the nominator will be informed and the article maindate will be updated when you first schedule. If you move the article to a new date the nominator will be notified again and the maindate updated but if you pull it completely the coordinator will need to clear the maindate on the talk page manually. Hawkeye7 (discuss) 20:27, 30 October 2026 (UTC)
Approved for trial (150 edits or 7 days, whichever happens first). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Zackmann (Talk to me/What I been doing) 22:57, 30 October 2026 (UTC)

Bot test run

  • Notifications: 3, 5, 5, 6, 6, 7, 8, 8 ...

Hawkeye7 (discuss) 22:55, 9 November 2026 (UTC)

Were any issues spotted? Anything that needed to be manually fixed? Zackmann (Talk to me/What I been doing) 00:14, 10 November 2026 (UTC)
The Bot had no instruction on how to handle articles that had already been run on the main page before. Some extra code was added to handle this situation:
4 16 Hawkeye7 (discuss) 01:42, 10 November 2026 (UTC)

VulpesBot 6

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:

  1. Lists all non-redirect subpages of Wikipedia:AI noticeboard, skipping the numbered archives.
  2. Compares each page's latest revision ID with the one stored from the previous run, and fetches text only for pages that changed. A normal day is a few listing requests plus one batched content request.
  3. Parses each case page and runs these checks:
    • Banner: missing or duplicate banner; case_name not matching the page title; cleanup/llmprod/conduct/case_type values the banner doesn't recognise (status values are read live from Template:AINB case banner/data); malformed or future original_file_date.
    • Structure: missing Discussion or Cleanup section; no {{AIC article list}}; missing {{user-ainb}} on user cases.
    • Filings: a filing heading dated later than its first signature (the move-script bug); unsigned filings; malformed date headings; filings out of order.
    • Cleanup tracker: {{AIC article row}} entries that render as "Unknown status", rows missing an article, duplicate rows, and cleanup marked completed while rows are still open.
    • Subpages: a /2-style subpage carrying a case banner; subpages with no parent case.
    • Index: banner statuses that disagree with the AINB/Cases or AINB/Closed row; cases missing from the index; cases on the wrong table; banner pages missing from Category:All AINB cases.
  4. Rewrites a single report page, User:VulpesBot/AINB format report. Errors and warnings are listed per case with a link; info-level findings are counted. Each entry shows when it was first seen, flags new entries, and lists issues resolved since the previous run. The edit summary gives the totals, e.g. "Bot: AINB format report, 42 open issues (3 new, 5 resolved)".

Discussion

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)

Seems like a great use for a bot. The use of a new package (Rwikibot) is certainly cause for concern, but then again so is any new code that is brought to a BRFA... Dr vulpes one word of caution (from a fellow bot op) is to make sure that your assumptions of how this package works are double checked in the trial. Sounds like you have tested it on the testwiki but just a word of caution based on mistakes I have made in the past... Other than that, this looks good for a trial. My understanding is that it will only run once a day? Given that I'm going to do a bit of an un-orthodox trial period since a trial of 100 edits would take quite some time... If issues arise during the trial that justify a hold/restart of the trial, {{ping|Zackmann08}} me and we can make that happen.
Approved for trial (50 edits or 14 days, whichever happens first). Please provide a link to the relevant contributions and/or diffs when the trial is complete. --Zackmann (Talk to me/What I been doing) 04:02, 30 October 2026 (UTC)
Thanks @Zackmann08, I'll take it slow with the roll out and try to start up this weekend. Dr vulpes (Talk) 04:33, 30 October 2026 (UTC)

POTDBot

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

Programming language(s): Zig

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)

Discussion

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)

It is the case because I already manually fixed the ~150 that were in some way broken, and more keep needing to be fixed. Avalyn (talk) 11:10, 17 September 2026 (UTC)
Apologies, just trying to make sure everything is accurately being described - are you going through the 8k transclusions and fixing what needs fixing in those transclusions? If that's the case, why are you editing 1 page per day? Would not the files going forward ostensibly be tagged with the correct templates/values? Primefac (talk) 18:20, 20 September 2026 (UTC)
The once page per day estimate is mostly just from new POTDs being added/modified. Avalyn (talk) 12:36, 24 September 2026 (UTC)
Again, forgive me for not understanding as POTD is not anywhere near my wheelhouse or something I even look at occasionally: if I understand the process correctly, when a picture is made POTD it has {{Picture of the day}} added to the file page, yes? This is done by the editor(s) who selected the page? Does it not regularly get added?
To ask for a specific page, File:Pin tumbler no key.svg is today's POTD, and it has {{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)
The template is often missed/incorrectly added, especially if there is already one present. A lot of times, the author will mistakenly use the date of their time zone instead of UTC, or miss adding a second tag. This bot would also turn the adding of the tag into an automatic process, making the process simpler for those creating POTDs. Avalyn (talk) 11:56, 28 September 2026 (UTC)
Also, if you want to see examples of POTDs that were in some way broken, you can go through my edit history, there's a lot there. Avalyn (talk) 12:00, 28 September 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) 21:27, 4 October 2026 (UTC)
Any update on the trial? Tenshi! (Talk page) 21:03, 18 October 2026 (UTC)
I am currently having trouble developing and testing the bot as I do not currently have access to a machine capable/willing to run a compiler. I am still working on it through Google Colab, however that is a slow process made even slower by my lack of available time. Avalyn (talk) 22:21, 18 October 2026 (UTC)

FengPurgeBot

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.

Discussion

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)

+. Each transclusion means a forced link update, and since maxlag alone does not stop one huge request from putting too much load on the servers or tying up the bot, it needs a per-job cap. I chose 1,500 because the discussion mentioned just under 1,200 redlinked categories, giving about 25% headroom, and because 1,500 had already been used for a similar task by Joe's Null Bot. If a higher limit works and is needed, I could raise it. A lower one is probably better for a trial, anyway... Fengrímur (talk) 08:12, 8 September 2026 (UTC)
I think I'm good for a trial, but I'd like a second opinion. Would be good to also make sure we have requested purges ready to go (i.e. is the BOTREQ request still ongoing?). Primefac (talk) 20:44, 13 September 2026 (UTC)
Not really ongoing. Depending on how much time people are willing to give this, I could continue working on my next planned bot — an updated version of this one — which would shove the problem off Wikipedia entirely. Basically, that means eliminating the human-in-the-loop that FengPurgeBot currently needs and just autonomously purging whenever it's needed and never when it's not supposed to (It's possible, I can confirm!). Naturally, I could also find pages for us that need requests specifically for this trial... Orrr we pause this for a bit until I publish the update for iFengPurgeBotPro. If it's up to me to decide, that's what I'd recommend, unless there’s a specific need for the bot in the next 1–2 weeks. Fengrímur (talk) 12:48, 14 September 2026 (UTC)
Does that mean you are withdrawing this for now? Primefac (talk) 18:22, 20 September 2026 (UTC)
No, I changed my mind. I’m way too busy right now to continue working on this bot’s replacement. I think it’s best if we move forward with this bot and its trial, and once I’ve finished my work on the other, previously mentioned bot (the updated version of this — more primitive — one) I shall file a separate BRFA. Let me know when a trial is ready or if you want me to look for much-needed purges myself. Fengrímur (talk) 12:33, 21 September 2026 (UTC)
Approved for trial (3 individual requests and 3 fan-outs, or 30 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. I do recognise there won't necessarily be a contribution log, but if there are any logs please link to them as well as the request diffs. Primefac (talk) 18:07, 27 September 2026 (UTC)
I will get to this soon. Fengrímur (talk) 18:30, 30 September 2026 (UTC)

Bots that have completed the trial period

ZackBot 15

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:

How to decides if an article has a image
It looks at one image only: the article’s lead image. Wikipedia already picks a lead image for every article, using a PageImages. That’s the image shown in search results, link previews, the apps, etc. Here it only picks from the section before the first heading, which is where the infobox and any top image are. It will never pick images marked as decoration, such as icons in navboxes or maintenance templates. The bot reads that choice. So an image further down the article never counts and an article with no lead image is treated (for purposes of this bot) as not having an image.
Some more logic
Issue Verdict Reason
Images with a word like map, flag, logo, icon, coat of arms, seal, signature, etc. in the filename Red X symbolN do not count 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 Red X symbolN do not count These are seldom a good image for the subject of the article so I err on the side of caution
A GIF exclamation mark  flagged for manual review 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 exclamation mark  flagged for manual review 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)
Green checkmarkY image request is removed No reason to have an pending image request for a page that is a redirect
  • Words must match whole, something like “Mapperley Park.jpg” is not treated as a map...

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)

Discussion

{{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)

Patience... barely even a week yet. Primefac (talk) 17:09, 15 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)

Trial complete. - Log of the results with diffs can be found at User:ZackBot/BRFA Log. A few things to note:
1) There were 7 questionable edits
Diff Page Analysis
Special:Diff/13858923082020 Donald Trump rally in Tulsa/TalkBot 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/13858923002019 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 photo or a photo showing the subject so 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/1385914645America First Party (1943)/Talk
Special:Diff/1385914668Anabaptist settlers/Talk
Special:Diff/1385914785Peter Angermann/Talk
Special:Diff/1385914934Loren Aragon/Talk
Special:Diff/1385915041Joan Gardy Artigas/Talk
2) The ImageReport worked as designed
As I noted above, there was one case that should have been sent for review that was not and that error has been fixed. The ImageReport did report numerous pages that might be suitable to have the photo request removed, but the bot cannot be sure that the image in the article meets the requirements so no change was made to any of those pages. A perfect example is Paola Antonelli which does have a photo but the request specifically asks for a better portrait of Paola Antonelli and the bot cannot confirm that has been achieved.
3) What next
Assuming no one else sees any glaring issues that prevent moving forward, I would like to request a more extensive trial. There are so many different permutations and combinations for this logic, I want to really test this, incrementally, in the wild before I am anywhere close to unleashing it. My thinking is a 500 edit extended trial, to be run in easily manageable groups of 50 at a time. For each of those 10 runs, I would manually inspect EVERY edit made. If an issue is found, revert it and fix the logic to prevent the issue from happening again.
Eager to hear any thoughts anyone may have! --Zackmann (Talk to me/What I been doing) 05:23, 16 November 2026 (UTC)

TenshiBot 13

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.

Discussion

@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)

Jonesey95 since the above ping was malformed. Tenshi! (Talk page) 19:48, 17 October 2026 (UTC)
Facepalm Facepalm . Thanks Tenshi Hinanawi.... My bad! --Zackmann (Talk to me/What I been doing) 19:50, 17 October 2026 (UTC)
This sounds like a great addition to the stable of Linter cleanup bots. I would like to see some test edits. – Jonesey95 (talk) 14:47, 18 October 2026 (UTC)
Approved for trial (100 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. sounds like this is a useful tool and worthy of giving a trial. @Tenshi Hinanawi: you are go for a trial! Zackmann (Talk to me/What I been doing) 15:04, 18 October 2026 (UTC)
Trial complete. Edits. A few of the initial edits had a bad replace which included a backslash, which was fixed during trial. Tenshi! (Talk page) 15:42, 18 October 2026 (UTC)
The Ichthus newsletter also had an extra div which should have been removed. Tenshi! (Talk page) 16:17, 18 October 2026 (UTC)
@Tenshi Hinanawi: it would seem that an extended trial is warranted as there were at least a could of issues. Going to let this sit for a bit and I encourage you to do some more local testing. If there are no objections from other editors in the next day or two I will gladly approve another trial! Zackmann (Talk to me/What I been doing) 17:10, 18 October 2026 (UTC)
I don't think it does, since these are minor faults that I would have caught during normal operation. The rest of the regexes were fine, it's just me failing to check the regexes thoroughly. Also, please don't ping, I have this watchlisted. Tenshi! (Talk page) 17:14, 18 October 2026 (UTC)
@Jonesey95: Do you mind having a look through the trial edits and giving your opinion? Tenshi! (Talk page) 15:22, 19 October 2026 (UTC)
The bot created new Linter errors and failed to fix a font error at User talk:Walkero159, User talk:Kris Skylar Storm Bryden, and similar pages. The bot missed an easy closing /div tag and some easy center tags at User talk:Robynduby; the /div is one of the patterns listed on the signature submissions page. The bot missed some easy Icththus-related errors at User talk:Fulldisclosure07. You can find regexes for many of these fixes at User:Jonesey95/AutoEd/linter.js. (edited to add: This is the entirety of my feedback. I checked the entire edit batch.) – Jonesey95 (talk) 13:50, 25 October 2026 (UTC)
  • 1&2: My fault for missing the font tag.
  • 3: The trial ran with only 4 regexes, not everything on signature submissions.
  • 4: It had only the January 2012 issue in mind. Tenshi! (Talk page) 14:04, 25 October 2026 (UTC)
    Previous bots have gotten negative feedback for visiting pages repeatedly. Legobot's Linter fixing bot deals with this, and with mistakenly creating new Linter issues with its changes, by checking to ensure that there are no remaining Linter errors on the page before saving. Your bot doesn't necessarily need to do that, but if there is any way to check to see if only font errors are left behind, or only obsolete tag errors, that would be helpful. In my script-assisted edits, I often leave only obsolete tags, hoping that Legobot will be able to clean up behind me in a single edit. – Jonesey95 (talk) 14:12, 25 October 2026 (UTC)
    I'm aware, hence I've been trying to add more regexes during this period. Tenshi! (Talk page) 14:28, 25 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)

Tenshi your assertion that this does not require any further testing or another trial has made me very hesitant to move forward. As Jonesey has pointed out, 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)
It's a little odd that the bot operator has not reverted all of the erroneous bot edits. People get busy with real life, though. Not a huge deal, but something that needs to be fixed at some point. – Jonesey95 (talk) 05:19, 27 October 2026 (UTC)
I don't think all of the trial edits require mass-reverting here? Where linter errors were introduced, they were removed, as for the ones it missed, it can be picked up in the next trial? Tenshi! (Talk page) 08:48, 27 October 2026 (UTC)
That is what I am recommending as part of the new trial. The bot should fix all Linter errors in pages like this one that have one new and one old Linter error (two errors total). It will need about 80 edits just to fix those edits, which is why I recommend a new trial of 200+ edits. – Jonesey95 (talk) 13:32, 27 October 2026 (UTC)
I no longer object given the situation has changed from minor errors like a typo and one extra div to 3/4 regexes were erroneous or missing replacements. Tenshi! (Talk page) 08:48, 27 October 2026 (UTC)
Zackmann08, another bot trial please, 200 edits? – Jonesey95 (talk) 19:07, 29 October 2026 (UTC)
{{BAG assistance needed}} Two weeks since the first trial was completed and 5 days without response from Zackmann08. Tenshi! (Talk page) 23:48, 31 October 2026 (UTC)
@Tenshi Hinanawi: I left a comment here saying that I would leave this to another BAG member to approve. Your attitude of feeling like your edits did not need to be checked left me with too many concerns to move forward. Another more senior member of the BAG is welcome to approve another trial, but I made clear with my last response that I would not be participating further. Zackmann (Talk to me/What I been doing) 01:16, 1 November 2026 (UTC)
I read that earlier, I didn't specifically request your input (though it would be welcome). Also, as I said earlier, I have this page watchlisted, so there's no need to ping. Tenshi! (Talk page) 12:15, 1 November 2026 (UTC)
Been busy, apologies.
Approved for extended trial (200 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Primefac (talk) 15:39, 1 November 2026 (UTC)
Trial complete. Edits. Six errors, 1 2 3 4 5 6. Tenshi! (Talk page) 19:04, 1 November 2026 (UTC)
@Jonesey95, could you please help review the latest trial edits one more time? @Tenshi Hinanawi, have you patched these errors? I'd like to extend the trial for another round, as the error rate is still high. Max (talk) 08:20, 7 November 2026 (UTC)
The errors were fixed during the trial. Please do not ping, as I have said twice already, I have this page watchlisted. Tenshi! (Talk page) 12:38, 7 November 2026 (UTC)
Apologies, I was directing the first question to Jonesey95 and the second to you, so I pinged both of you. I should have remembered your earlier request. Didn't mean to bother you. Max (talk) 14:05, 7 November 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)

VWF bot 11

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.

Discussion

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)

Trial complete. See contributions capped at 50. Vanderwaalforces (talk) 18:34, 11 October 2026 (UTC)
I’ve just gone through them all as the original requester at BOTR, and can’t see any issues with the edits made - they all cleanly removed the dates as required, and all were dates in the past Danners430 tweaks made 21:53, 11 October 2026 (UTC)
I don't have any concerns with the task itself, but the operator has been blocked from article-space indefinitely during the BRFA. I'm not sure how BAG feels about that in regards to how this BRFA should be handled? Tenshi! (Talk page) 21:00, 18 October 2026 (UTC)
The bot is not the user, and the edits being made by the bot are specific and (as far as I am aware) not really something where using AI would matter? Primefac (talk) 21:03, 18 October 2026 (UTC)
I agree it doesn't matter in this context, I was thinking about reverting potential errant bot edits and how the operator would comply with WP:BOTACC, given they would have to make edit requests, etc. Tenshi! (Talk page) 21:07, 18 October 2026 (UTC)
That is indeed what would need to happen, either page-by-page or as a mass rollback request. Primefac (talk) 21:09, 18 October 2026 (UTC)
Non-BAG member comment - WP:BOTPOL states, 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 operator and 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.
To be 100% clear, I do not oppose Vanderwaalforces being a bot operator, nor do I think this particular bot has any technical reasons not to be approved. VWF has shown this year that they have the technical aptitude to run bots, and that they are capable of coming up with and coding useful bot tasks that benefit the community. If they are able to resolve their sanctions, I would love to see them continue to develop bots, and would love to see them continue in the bot operator community. phuzion (talk) 18:34, 22 October 2026 (UTC)
A few thoughts on the above:
  • 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).
That being said, VWF seems to have a case of ANI flu so there's not really any rush to decide the matter. It might be worth starting a general discussion on the topic at WP:BOTN though.
On hold. (for the bots and tables) for now until some combination of VWF returning, getting their sanctions lifted, or BAG clarifying the above concerns are met. Primefac (talk) 22:38, 26 October 2026 (UTC)
VWF bot's tasks 1, 2 and 3 are using code I wrote. Since Vanderwaalforces hasn't been responding, I'd like to move them back to my bot. I messaged him on Discord a few days ago, and I'll file a BRFA to take them over if I don't hear back. Max (talk) 10:57, 6 November 2026 (UTC)

Approved requests

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.

Denied requests

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.

Expired/withdrawn requests

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.