Anycubic Forge Console Third-party Client Notice Source code & license

Anycubic Forge Console Third-Party Client Notice

Convenience translation. If this English translation differs from the Chinese original, the Chinese original prevails.

Published: August 15, 2026
Effective: August 15, 2026

Anycubic Forge Console (the “Client”) is an unofficial third-party client compatible with Anycubic printers. Read this notice before signing in, connecting OrcaSlicer, configuring AI, transferring files, viewing camera or time-lapse content, or sending device commands.

1. Unofficial status

The Client is not an official app, website, firmware component, or support tool published by Shenzhen Anycubic Technology Co., Ltd. or its affiliates (“Anycubic”). There is no affiliation, agency, reseller, joint-venture, warranty, certification, sponsorship, or official-support relationship unless expressly stated in writing. Anycubic names, product names, marks, and service names belong to their respective owners and are used solely to identify compatibility.

This notice does not replace Anycubic's terms, privacy policy, manuals, warranty terms, or other official rules.

2. Technical boundaries

The Client uses Anycubic cloud services, MQTT, device messages, and video services. Some interfaces are not public, stable third-party APIs. Authentication, protocols, rate limits, data formats, or firmware behavior may change without notice and can delay, break, or permanently disable features.

A successful page response may mean only that a command was sent or accepted by the cloud. Confirm the final state at the printer. The Client does not bypass account, region, device, access-control, or security restrictions and must not be used for unauthorized access, interference, bulk abuse, or unlawful activity.

3. Accounts and authorization

Use only accounts, printers, cameras, files, and recordings you own or are expressly authorized to manage. Treat passwords, access tokens, session cookies, Orca API keys, AI provider keys, and similar credentials as sensitive. Multiple official or third-party clients can cause token changes, connection conflicts, delayed state, or failed controls. Account recovery, suspension, deletion, and official cloud-data management remain Anycubic's responsibility.

4. Physical-device risks

Remote commands can have physical consequences, including burns, fire, pinching, collisions, jams, equipment damage, failed prints, wasted material, overheating, and irreversible file deletion. Network delay, disconnection, stale state, or concurrent clients can cause commands to arrive late, twice, out of order, or not at all.

Before operating a printer:

  1. verify the target printer, job, parameters, and surroundings;
  2. test new or changed features on a non-critical job with local supervision;
  3. follow the printer manual and material, ventilation, and fire-safety requirements;
  4. never treat the Client as the only emergency stop or safety alarm;
  5. stop remote operation if the interface and physical printer disagree; and
  6. avoid conflicting control from multiple clients.

5. Files, logs, cameras, and AI

You must have the right to upload, analyze, print, download, or share files, models, images, recordings, logs, and reports. Logs may include device identifiers, network information, filenames, activity, and error context. Cameras may capture homes, workplaces, people, or confidential material. Obtain required permissions and limit the camera's field of view.

AI model setup sends a real minimal validation request and can consume tokens or plan quota. Filament calibration sends 1–20 selected images in a multi-image request and may incur substantial vision-token usage. The model must support vision and multiple images. AI conclusions are suggestions only; verify them with a limited test print.

6. Third-party services and privacy

Features may depend on Anycubic, Agora/Shengwang, Anycubic Wiki, your selected AI provider, and hosting or storage providers. They may process network, account, device, file, channel, or request data under their own terms and privacy policies. See the Privacy Policy for details.

The Client does not impersonate an approved tool or evade provider restrictions. If a Coding Plan or similar subscription rejects the request, use an access method permitted by that provider.

7. Compatibility and availability

No guarantee is made that every function will be error-free, uninterrupted, real-time, or compatible with every account, region, model, firmware, and slicer. If a function behaves unexpectedly, stop repeated operations and confirm the printer state through its local controls or Anycubic's official app.

8. Responsibility

You are responsible for account authorization, commands, parameters, files, physical supervision, and compliance with applicable law and third-party terms. To the extent permitted by law, maintainers and service operators are not liable for losses caused by unauthorized use, incorrect operation, incompatible changes, third-party outages, network failures, or reliance on AI suggestions. Nothing in this notice excludes liability that cannot legally be excluded.

9. Open-source license and trademarks

The source code is licensed under the GNU Affero General Public License v3.0. The license governs use, copying, modification, and distribution of the software; it does not grant rights to Anycubic trademarks, cloud services, accounts, firmware, or proprietary interfaces. See NOTICE for attribution and the non-affiliation statement.

10. Acceptance and contact

By continuing to use the Client, you acknowledge this unofficial status, the compatibility limits, and the physical-device risks described above. If you do not accept them, stop using the Client. Report legal, security, or compatibility concerns through the project's published repository contact channels.