BiliBiliToolPro

BiliTool

Automate recurring Bilibili tasks across one or more accounts.

BiliTool runs scheduled Bilibili activities through the platform’s APIs. Use the Web panel to manage accounts, configuration, schedules, and execution logs, or run tasks with the Console host and your preferred scheduler.

It supports QR-code login and cookie updates, multiple Bilibili accounts, daily experience tasks, live-room and manga activities, VIP benefits, B-coin voucher charging, batch unfollowing, and optional notifications. Each activity can be configured independently; availability depends on your account and Bilibili’s current services.

Get started

Choose one deployment guide, start the application, and run the Login task to add a Bilibili account by scanning its QR code. Then configure the tasks and schedules you want to use.

The GitHub Actions task workflows are stored under platforms/gitHubActions/bak/, not in the active repository workflows. That guide describes an archived recipe, not a ready-to-enable deployment.

For settings, environment variables, and task-specific options, see the configuration guide. For troubleshooting, see the FAQ.

Available tasks

A task is a runnable unit of work. Some tasks contain several individual activities; enable only the ones you need.

Task eligibility, rewards, and timing are controlled by Bilibili and may change. Check the configuration guide for switches, schedules, and creator IDs.

Multiple accounts

Run the Login task again to add another Bilibili account. Where the cookie is stored depends on the host:

• Web panel: accounts are managed in the panel and stored in config/BiliBiliTool.db.
• Qinglong: cookies are saved as environment variables such as Ray_BiliBiliCookies__0, Ray_BiliBiliCookies__1, and so on.
• Console and other non-Web hosts: the default local account file is cookies.json:

{
  "BiliBiliCookies": [
    "cookie1",
    "cookie2"
  ]
}

The panel administrator login is separate from the Bilibili accounts used for tasks. Treat both administrator credentials and Bilibili cookies as secrets.

Notifications

Optional execution notifications support Telegram, PushPlus, WeCom, DingTalk, Microsoft Teams, ServerChan, CoolPush, and custom API endpoints. Delivery depends on the provider and your configuration. See notification settings for setup.

Help and releases

Before reporting a problem, update to the latest release and search the FAQ, configuration guide, issues, and discussions. Open an issue for a reproducible bug or feature request; use discussions for questions and ideas. Never post cookies, tokens, or passwords.

Follow releases for published versions and the issue tracker for ongoing work. Merges to main produce preview Docker images; stable releases are published separately.

Contribute

Code and documentation contributions are welcome:

For test naming, levels, and safe local execution, see the testing guide.

1. Search existing issues before starting. For substantial or uncertain changes, open an issue to discuss the approach first.
2. Fork the repository and make changes based on main.
3. Open a pull request targeting main with a clear title and description. After review and successful checks, maintainers squash-merge accepted changes.

Documentation fixes, clarifications, and corrections are just as valuable as code changes.

Support the project

If BiliTool helps you, you can support its maintenance through the donation QR code below.

Every sponsorship is a vote for your ideal world!

(If you would like to join the discussion group, please include your WeChat ID in the message when making a donation.)

Some creator-ID settings use the maintainer’s Bilibili ID as a default configuration value. You can change those settings through the configuration file, secrets, or environment variables to support a different creator.

Acknowledgments and references

• Bilibili
• SocialSisterYi/bilibili-API-collect
• JunzhouLiu/BILIBILI-HELPER

Thanks to JetBrains for a free open-source license:

Thanks to YxVM, NodeSeekDev, and DartNode for supporting the project’s test servers.

Thanks to everyone who has starred this project: