AntBytes Agent
AntBytes Agent tray icon

Endpoint visibility and support tickets in one quiet control flow.

The AntBytes Agent connects customer computers to the AntBytesCC admin console. It checks in on a schedule, reports local support requests, keeps offline work queued, and lets the admin team track every open issue from one protected dashboard.

Download Windows Agent View Latest JSON Open S2E Open Admin Issues
AntBytesCC // Agent Flow
1 Install Enroll endpoint with API URL, key, organization, and site.
2 Check In Hostname, user, IP, OS, uptime, disk, and agent version report in.
3 Report Issues Users can send AntBytes Assist requests from the endpoint.
4 Track Work Admins move tickets from open to in progress to completed.
Download

Get the current agent build

Use the stable build for regular Windows installs. Use the candidate build only when testing the newest assist and migration work.

StableWindows

Latest Windows Agent

Version 0.4.6 • 5.2 MB • released 2026-08-31T19:11:27Z

AntBytesAgent-v0.4.6-owner-desktop-alerts.exe
Download Stable Manifest
CandidateTesting

Assist Candidate

Version 0.4.4 • windows • 7.5 MB

AntBytesAgent-v0.4.4-common-problems-candidate.exe
Download Candidate Manifest
macOSRelease Candidate

Mac Candidate Builds

Apple Silicon and Intel macOS candidate builds are available for testing the shared check-in and common-problem catalog flow.

AntBytesAgent-v0.4.4-common-problems-candidate-macos-arm64
Apple Silicon Intel
Windows Security

Smart App Control and unsigned builds

Some Windows 11 machines block unsigned agent builds before the agent can open. If Smart App Control says it cannot verify the publisher, use this as a security/publishing issue, not an agent crash.

Immediate technician path

Use PowerShell as Administrator. If the file is blocked, Windows Security may need Smart App Control turned off before this unsigned test build can run.

What to verify

After install, confirm the agent exists at C:\Program Files\AntBytes\Agent\AntBytesAgent.exe and the scheduled task is present.

Permanent fix

Production Windows builds should be signed with a trusted code-signing certificate so Windows can verify AntBytes as the publisher.

Smart App Control has no per-app allow button for an unknown unsigned executable.
Turning Smart App Control off is a device-level decision and should be treated as temporary for test installs.
The signing workflow is documented in the agent source so future releases can move toward verified publisher installs.
Updates by OS

How update checks pick the right build

Agents report their current version and OS to the API. Public download manifests expose stable Windows releases and OS-specific candidate channels for testing newer builds.

Stable first, candidate for assist testing Available

Windows

Production Windows installs use /download/agent/latest and latest.json. Candidate testing can use /download/agent/candidate/windows.

AntBytesAgent-v0.4.4-common-problems-candidate.exe

Version 0.4.4 • 7.5 MB • 2026-08-28T01:38:05Z

Manifest Download
Candidate build Available

macOS Apple Silicon

Apple Silicon Macs use the arm64 candidate endpoint when a signed or test build has been published.

AntBytesAgent-v0.4.4-common-problems-candidate-macos-arm64

Version 0.4.4 • 7.1 MB • 2026-08-28T01:38:05Z

Manifest Download
Candidate build Available

macOS Intel

Intel Macs use the x64 candidate endpoint so update checks do not pull an Apple Silicon binary.

AntBytesAgent-v0.4.4-common-problems-candidate-macos-x64

Version 0.4.4 • 7.3 MB • 2026-08-28T01:38:05Z

Manifest Download
Candidate build Not published

macOS Universal

Universal builds can serve mixed Mac fleets once the combined binary is built, signed, and published.

No macOS Universal candidate artifact is published yet.

Request Build
Installed agents call POST /agent-api/agent-version with their current version during the normal check-in cycle.
The admin API answers with current_version, latest_version, update_available, and download_url.
The public download layer now exposes OS-specific candidate manifests, so Windows and Mac test builds can be published without mixing binaries.
How It Works

From endpoint to resolved ticket

The product is intentionally simple: agents report in, issues enter the queue, admins triage the work, and endpoints receive updates when work changes state.

01

Enroll the machine

Install the agent with the AntBytes API URL, API key, organization, and site so the endpoint is tied to the right customer environment.

02

Collect status

The agent sends machine identity, signed-in user, network details, OS, uptime, disk usage, and version data on a recurring schedule.

03

Create support requests

Users can submit AntBytes Assist requests from the endpoint. Offline requests stay queued locally and retry when the machine reconnects.

04

Resolve in the admin console

The admin Issues page shows open and in-progress work, supports priority/category updates, and stores resolution notes for follow-up.

Learn With Ant

Learning can ride along with agent check-ins

When agents check in, the API now includes a Learn With Ant category. The first item is an Introduction video placeholder, ready for the video you still need to create.

VideoPlanned

Introduction

A short video introduction for new learners, technology students, and agent users who need a clear first step.

Open S2E
Admin Console

Operational views

These protected views help the admin computer act as the central command point for open issues and connected devices.

IssuesTrack new, open, in-progress, and completed tickets. DevicesReview endpoints, recent check-ins, and device issue history. ReportsSee client, site, priority, and monthly issue summaries. EnrollmentsCreate keys for new customer machines and sites. AlertsManage new issue and urgent issue notification policy. MaintenanceQueue and monitor endpoint maintenance actions.
Install Notes

What a technician needs

Before installing the agent, have these values ready from the customer environment.

API URL

Use https://api.antbytes.io for production installs.

Agent Key

Use the approved AntBytes agent API key or enrollment flow. Do not paste secrets into public tickets or screenshots.

Organization and Site

Set the customer name and location so tickets and reports land in the correct client bucket.