Online Resources

Online Resources provides community content inside Helios. Anyone can browse the gallery. Sign in to download executable resources, including public scripts and official apps, and for likes, restricted content, publishing, or author controls.

Content Types

Browse and Use

---

Authenticated .gbc and .gbc3 resources are delivered by drag and drop rather than saved as normal downloads. Drag a Titan Two GPC/GBC resource or .git translator to a Titan Bridge memory slot. Drag a GPC 3 GPC3/GBC3 resource or .ipt translator to a GPC 3 slot. Helios compiles published controller source before delivering compatible bytecode.

Downloaded files are placed in the relevant local working or model area. Review community scripts before running them and use content only from authors you trust.

Official Apps

Official Apps show Launch instead of a normal download action. On first launch, Helios downloads and installs the current release into its managed local area, then starts it. Later launches reuse the installed matching release; when the published release changes, Helios downloads the new version before launching.

An already-running app can continue for up to 12 hours after a newer release is published. Relaunch through Online Resources to install and use the current release; this does not require reinstalling Helios.

Only apps published as official Helios resources appear in this category. Community publishing does not accept arbitrary executable applications.

Keep Online Resources loaded while using an app it launched. Unloading that plugin closes the official apps it hosts; hiding its panel or closing an MCP connection does not unload it.

Visibility and Access

• Public: visible and downloadable where access permits.
• Locked: visible, but download or drag delivery requires authorization.
• Private: visible only to authorized users.

Authors with both Discord and a verified email linked can open Manage Access on their own restricted resources to grant or revoke users, set an optional expiry, import or export account IDs, and copy the Resource ID. Enter a 17–20 digit Discord ID or a 21-digit Input Sense ID. Recipients can copy their Input Sense ID from Preferences → Account and can receive access without linking Discord. If an ID is not found, ask the recipient to sign in to the current Helios release and copy it again.

For a trusted external service, use the key icon beside Refresh to create, rotate, or revoke a personal integration key. The secret is displayed once. See the Online Resources API for the supported server-side workflow.

Publishing

Publishing requires sign-in, Developer Mode in Preferences, and both a linked Discord account and a verified email on the same Input Sense account. The Discord account must be at least 90 days old (shown as 3 months in Helios), and the Input Sense account must be at least 7 days old. The Account page shows both account ages. Managing existing resources and integration keys also requires both sign-in methods to remain linked.

Use Publish Script, Publish Environment, or Publish ONNX Weights from File Explorer or Online Resources. Provide a clear name, version, description, tags, instructions, visibility, and optional header image. Weight uploads must identify their task as detect, pose, or segment. Existing content can be edited or replaced by its author. Bytecode is produced by Helios from publishable controller source; .gbc and .gbc3 files are not direct upload sources.

Publishing limits are:

• CV Python .py and CV C++ .dll scripts: up to 100 MiB;
• other script and environment files: up to 4 MiB;
• ONNX or ENNX model weights: up to 300 MiB;
• official Windows applications: up to 300 MiB for Input Sense publishers;
• JPG, PNG, or WebP header images: up to 4 MiB and from 100×100 through 4096×4096 pixels;
• successful uploads: up to 15 per hour and 60 per day per account;
• successful normal resource downloads: up to 30 per hour per account, or per network address when signed out.

The default account allowance is 50 published resources; your account may have a different allowance. Helios reports when that allowance is reached. Rate limits use rolling time windows, so wait before retrying after a limit message.

Do not publish credentials, private keys, personal data, duplicate copies of existing content, or files you do not have permission to distribute.

For large model and official-app uploads, keep Helios open and online until the upload finishes. Cancelling or losing the connection may require retrying the upload.

Compatible AI clients can also inspect a local file and explicitly publish or update it through the MCP publishing workflow. The same account requirements, limits, and review process apply.

Review Guidelines

Before an upload begins, Helios checks its name, description, instructions, tags, and filename. If they match review criteria, Helios warns that the resource requires manual review and lets you cancel or upload it for review. A submitted item may show IN REVIEW and may or may not be approved.

To avoid unnecessary review:

• use original, AI-generated, or unrelated imagery rather than game screenshots, artwork, logos, characters, or promotional material;
• do not use purchase, buying, pricing, or similar sales language in resource details; and
• use neutral, generic wording instead of exact game titles.

Only upload an image when you own it or have the necessary rights to publish it. Resources under review do not use their submitted images publicly. Existing authorized users may retain access while an item is reviewed, but the item is not generally listed until approved.

While a resource is under review, authors cannot grant access to new users, renew expired access, replace its uploaded file, or delete it. Existing active author-managed access can still be edited or revoked. Wait for review to finish before adding recipients or changing the file.

Troubleshooting

• Account required: sign in again and click Refresh.
• Publishing or author controls unavailable: enable Developer Mode and link both Discord and a verified email under Preferences → Account. For new uploads, also check the account-age requirements above.
• Download not allowed: request access from the author when the item is Locked or Private.
• Drag does not start: sign in, confirm access, and drag to the compatible Titan Bridge or GPC 3 slot while that destination accepts changes.
• Existing local file: choose whether to keep or replace it.
• Duplicate weights: Helios opens the existing matching entry so it can be reviewed or updated instead of creating another copy.
• Upload requires review: revise the text, tags, filename, or image to follow the review guidelines, or continue only if you want to submit it for manual review.
• Access grant rejected for an item in review: wait for approval before adding a recipient or renewing expired access.
• Resource artwork looks stale: try Preferences → Other → Cache → Clear all caches, wait for cleanup, then refresh Online Resources.
• Upload interrupted: keep Helios open, confirm the connection is stable, and retry from the publishing dialog.
• Environment setup fails: open the installation details and check package/Python compatibility, connectivity, and disk space. A system Python installation is not required to create a managed environment. See Python Environments.
• Official App is unavailable: refresh the gallery, update Helios, and retry. Sign in if the item requires account access. If a launch download expires or fails, check connectivity, the Windows clock, free disk space, and folder access, then click Launch again.
• API key was exposed: rotate it immediately from the key dialog.