Agent

The Furl agent runs on your endpoints to provide environment context, health status, and management capabilities. Choose your platform below for system requirements, deployment, and installation instructions.

Deploy configuration before installing the agent. This ensures connectivity and permissions are in place when the agent starts. Each platform’s prerequisites are covered in its install guide.

Install guides

Agent on Windows — system requirements, automated deployment (MDM, Group Policy, silent install), and manual installation for Windows endpoints.
Agent on macOS — system requirements, configuration, MDM deployment, and manual installation for macOS endpoints.
Agent on Linux — system requirements, installation via the self-extracting installer, and configuration for Linux endpoints (Ubuntu and Debian).

Enrollment secret

Every organization has one agent enrollment secret. You can view or regenerate it in your dashboard under Settings → Agent, in the Agent Deployment card.

What it is for. The enrollment secret tells Furl which organization an endpoint belongs to. When the agent starts for the first time, it presents the secret to enroll. Furl looks up the organization that owns that secret, registers the endpoint there, and issues the endpoint its own identity. The agent’s management component also sends the secret with every request it makes to Furl, so the secret must remain valid for the life of the install.

Where it lives. You never type the secret in by hand. It is embedded in every configuration file you download from Settings → Agent (the Windows .reg file, the macOS .plist or .mobileconfig, and the Linux furl-agent.conf). Deploying that configuration to an endpoint is what gives the agent the secret. This is why the configuration must be in place before the agent starts.

What it is not. The secret is shared by every endpoint in your organization. It is not a per-device credential and does not identify an individual endpoint. Anyone who has it can enroll a device into your organization, so treat downloaded configuration files as sensitive and distribute them only through your MDM or deployment tooling.

Regenerating it. Use the regenerate button next to the secret in Settings → Agent, then save the settings. After you save:

Configuration files downloaded earlier no longer work. Download fresh configuration and update your MDM or deployment packages before enrolling new endpoints.
Endpoints that are already enrolled keep reporting telemetry, but their management traffic authenticates with the secret in their on-disk configuration. Deploy the new configuration to existing endpoints as well.

FAQ

What network connectivity does the agent need?

Outbound HTTPS to Furl’s cloud infrastructure. Specific endpoints and ports are documented in your dashboard’s agent configuration.

Can I install the agent on virtual machines?

Yes — VMs running supported operating systems are fully supported.

How do I update the agent?

Updates are currently manual. Re-deploy the latest installer the same way you originally deployed the agent (MDM, Group Policy, or manual install over the existing installation).

What data does the agent collect?

Endpoint telemetry as configured by your organization’s policy. Full data-handling details are available in your Furl dashboard under compliance documentation.

Troubleshooting

The agent shows “Not running” status

Symptoms: The agent’s tray or menu-bar icon is present but reports Status: Not running.

Solutions:

Confirm the configuration was deployed correctly.
Check system permissions — on macOS, verify Full Disk Access in particular.
Review the agent logs (see your platform’s install guide) for specific errors.
Verify network connectivity to Furl’s services.

Getting more help

If issues persist:

Collect the relevant log files.
Note the exact error messages and symptoms.
Include system information (OS version and architecture).
Contact Furl support at support@furl.ai.

For additional support, contact support@furl.ai.