When an agent’s behavior needs to change — a new certificate path, a different polling interval, an updated script environment — you no longer need SSH access to the host. Config push delivers a versioned configuration revision directly to the agent from the dashboard, and tracks every step from queue to confirmation.

​
What it is

You edit the agent’s configuration in the dashboard and submit it as a revision. The agent picks up the pending revision on its next poll, applies it, and reports back. You can see the delivery status in real time on the agent’s detail page. Every push — and every agent acknowledgement — is written to your audit log so you can prove what changed, when, and which operator authorized it.

​
When to use it

  • Change the certificate directory path the agent monitors without logging into the host.
  • Update polling intervals or connection parameters across a fleet of agents from one place.
  • Roll out a new environment variable for deployment scripts running on the agent.
  • Confirm a configuration change landed on a remote agent before a planned maintenance window.
  • Audit which operator last changed a given agent’s configuration and exactly what they sent.

​
Set it up

1

Open the agent detail page

Go to Infrastructure > Agents and click the agent you want to update.
2

Click Push Config

Click the Push Config button to open the configuration editor. The editor shows the agent’s current configuration as JSON.
3

Edit the configuration

Make your changes in the editor. The diff view on the right shows what will change compared to the last push.
4

Submit the push

Click Push. The revision is queued immediately and the agent’s desired state is updated.
5

Monitor delivery

Watch the Push history tab. The status transitions from Pending to Delivered when the agent polls and acknowledges receipt, then to Applied when the agent confirms the configuration was applied successfully.

​
What you’ll see

The Push history tab on the agent detail page lists every revision in reverse chronological order, with timestamps and status badges. Click any revision to see the full configuration that was sent and the diff against the prior push. If a push fails, the agent reports an error message visible in the revision detail.
If two operators push configuration in quick succession, the agent will only apply the most recent revision. The superseded push remains in the history for audit purposes but will never be applied.

Custom Deployment Scripts

Scripts that may reference configuration values pushed via this mechanism.