nodrail

Using Nodrail Cloud

Use a shared workspace to review exceptions, publish policies and investigate decisions from connected agents. To write your first APF file on your own machine, start with the local engine.

A Nodrail Cloud workspace has one or more environments, such as development and production. Each environment has its own agents, rules, requests and history. Switch workspace or environment from the menu at the top of the page; the navigation on the left is the same in each.

PageWhat it answers
OverviewWhat needs me now, is everything healthy, and what happened today?
ApprovalsWhich requests are waiting for a person?
AgentsWhich agents and installations are connected, and how do I connect one?
PoliciesWhich rules decide what agents may do?
ActivityWhat did an agent do, and what was decided?
InsightsWhich approvals could be rules, and are the rules working?
Team, SettingsWho can do what, and the plan and its usage.

What you see depends on your role. Owners, Admins and Policy managers see every agent in the workspace. Approvers and Viewers see the agents assigned to them and their own actions.

Overview

The first page answers three questions from top to bottom. Waiting for you: the first open requests, with the same Allow once and Deny buttons as Approvals. Health: how many agents are reporting, the plan's usage this month and any problems. Last 24 hours: actions allowed, denied and waiting for review, each with a 7-day trend and a link to the matching list in Activity, and the most recent decisions.

Approvals

A covered action that no rule allows or denies, or that a rule sends for review, waits in Approvals until a person decides or the request expires an hour later. Each row shows the agent and installation, the action and resource, why it waits and when it was asked. Open a row to see the parameters the agent sent and when the request expires.

  • Allow once allows this one request: the same agent, installation, operation, resource and parameters. The agent asks again next time.
  • Always allow…, in the menu beside Allow once, allows the request and adds a rule for the same agent, installation, action and resource, after a confirmation that shows the rule. Open requests the new rule covers are allowed too. It is offered to people who can both decide requests and write rules: Owners and Admins.
  • Deny denies the request, and the covered call stays blocked.

A request leaves the list when someone decides it, when it expires, or when it is closed: the agent was paused, its credential was revoked, a published rule changed the answer, or the integration withdrew it because the agent stopped waiting. Integrations withdraw a request with the Runtime API.

Approving a request does not change your rules, and adding a rule does not decide a request on its own: Always allow… does both, on purpose and with a confirmation.

Policies

Policies has four tabs for the selected environment.

  • Rules lists permission rules. Use New rule to create one in the form.
  • Gates (preview) lists the active prerequisites: which steps of a run must pass before an action. Add, edit or remove one in a form.
  • Budgets (preview) lists the active limits: how many tool calls, tokens or dollars a step or run may use. Add, edit or remove one in a form.
  • YAML is where people with policy-write access declare all three. Put rule:, gate: and budget: entries at the top level of the same file. Choose Review changes, then Publish rules to apply the reviewed file to this environment. Everyone with read access can inspect the policy. Agent Policy Format

The editor checks the file as you type and points to problems by line and column. Cloud checks it again before publication and shows which entries would be added, changed or removed. Publishing replaces the environment’s active policy with the reviewed file. Start from the current YAML to preserve entries you want to keep. If an open request’s outcome changes, the agent must ask again.

Import YAML and Export YAML move a whole file in and out, for example to keep the rules in a repository and test them with the open-source engine.

Activity

Activity is the history of the environment, with two views.

  • Events lists each recorded event, newest first: decisions on agents' actions, outcomes your integrations reported, and changes made in the workspace.
  • Runs groups actions by piece of work, for integrations that record runs. Open a run for its timeline of steps, actions and verdicts. See Runs, gates and budgets (preview).

Both views share the filters: a search, the agent, the outcome (allowed, denied, waiting for review, expired or closed) and the time range (24 hours, 7 days, 30 days or all). Events can also be narrowed to authorization decisions, events with a report from your integration, or workspace changes. The filters are part of the page address, so you can share a filtered list as a link.

Select an event to open its details in a side panel: agent and installation, operation, resource, parameters, what recorded it, the time and the request ID, the rule that decided it when one did, and any outcome your integration reported. A decision is not proof that a tool ran; a report is your integration's word.

Export downloads the filtered events as CSV or JSON, newest first, up to 10,000 events. The columns are time_utc, agent, installation, tool, operation, resource, outcome, decided_by, reason, run and request_id. Each export is recorded in the audit log with its format, filters and row count.

Insights

Insights looks back over the last 7, 30 or 90 days. Each section asks a question and leads to something to do.

  • Which approvals could be a rule? The same agent and installation asking for the same action on the same resource, approved once at least three times in the window and never denied. Create rule adds the same exact rule as Always allow…, after the same confirmation; it needs permission to write rules. Dismiss hides the suggestion for everyone in the environment.
  • How much are people asked to approve? Actions decided by rules and by people, time to decide (median and 9 in 10), and requests that expired or were withdrawn.
  • Are the rules doing the work? The rules that decided the most actions, and the rules that never matched in the window.
  • Where do gates and budgets stop work? and How do agent teams work together? For workspaces that use runs, gates and budgets (preview).
  • Is anything stuck or uncovered right now? Agents that stopped reporting, and installations whose actions mostly match no rule. This section is about now, whatever the window.

Usage

Each governed action counts once against the workspace's monthly allowance, whatever the decision. Run steps (preview) don't use actions: a workspace can record as many steps a month as its plan has actions. Overview shows both, and Settings shows the plan. See Pricing for what counts and what happens at the limit.