SentinelX

Delete a file or (with recursive=true) a directory. The path must resolve under an `rw` file_ops entry. The agent ALWAYS takes a backup before destroying anything: a file is copied to a sibling `.bak.<timestamp>`, a directory is archived to a sibling `.bak.<timestamp>.tar.gz`. If the backup cannot be made the delete is refused (`backup_failed`) — nothing is destroyed without a recovery path. Deleting a directory requires `recursive=true` explicitly. Without it, a directory is rejected with `is_directory`. This makes accidental `rm -rf`-shaped mistakes impossible to trigger by a single confused call.

sentinel_delete

Edit a file on the connected host using safe, structured operations. Modes: - replace literal old -> new_text - regex pattern -> new_text - replace-block start_marker..end_marker -> new_text - append append new_text to file - prepend prepend new_text to file - write overwrite file with new_text For large content use the chunked variant: sentinel_edit_upload_init, sentinel_edit_upload_file, sentinel_edit_upload_complete. Security: `path` must resolve under a file_ops entry whose access is `rw` in the agent's config (the unified r/rw path model). A path that is only readable (access: r), or outside the allowlist, or that escapes it via `..`/symlink, is rejected with path_not_allowed — edit is a mutation and is gated exactly like move/copy/delete. This is enforced agent-side, after canonicalizing symlinks.

sentinel_edit

Return the user's currently-configured default host (if any). The response carries both the stored host_id AND a flag indicating whether that host is currently connected, so the caller knows whether tool calls without explicit host_id will succeed. Returns: {"ok": True, "default_host_id": "<id> or null", "is_connected": true|false|null} is_connected is null when no default is set.

sentinel_get_default_host

List DNS records in a Cloudflare zone, optionally filtered. Use this to inspect existing records and to get the record `id` values needed by update_record and delete_record. Returns up to 100 records per call; if a zone has more, narrow down with the `type` or `name` filters.

cloudflare_dns_list_records

List every Cloudflare zone the saved token has access to. Use this first to discover zone IDs before listing or modifying records. The result includes each zone's id, name, status, and whether it's paused.

cloudflare_dns_list_zones

List entries in a directory on the target host. Output is structured (each entry has name/type/size/mtime), unlike sentinel_exec("ls -la") which returns opaque text. Always skips common noise directories (.git, __pycache__, node_modules, .venv, .pytest_cache, dist, build, etc.) regardless of show_hidden.

sentinel_list

List the saved integrations for the calling user. Use this when you need to know which integrations are available before calling a provider tool (telegram_send_message, resend_send_email, cloudflare_dns_*). All those tools take an `integration_name`; this is how to discover the valid names. Returns: { "ok": true, "items": [ { "name": "<user-chosen alias>", "provider": "cloudflare" | "telegram" | "resend", "created_at": "<ISO8601>" }, ... ], "count": <int> } The returned data deliberately does NOT include each integration's metadata (e.g. Telegram default_chat_id, Resend default_from) nor the encrypted credentials. Those are managed exclusively from the dashboard UI by the authenticated user, and the LLM cannot read or modify them via tools. If the user has no integrations, returns an empty list with count zero — not an error.

list_integrations

List all hosts currently connected for the authenticated user. Each host entry includes: - host_id: stable unique id, generated at install time - hostname: system hostname reported by the agent at handshake - label: user-defined alias (null if none set; see sentinel_set_host_label) - session_id: internal session identifier - connected_at: ISO timestamp of when the agent connected - agent_version: version reported by the agent - capabilities: ops the agent supports Other tools' `host_id` parameter accepts any of host_id, label, or hostname. Resolution priority is exact host_id → label → hostname. Returns {"ok": true, "hosts": [...], "count": N}.

sentinel_list_hosts

Move or rename a file or directory on the target host. BOTH `src` and `dst` must resolve under a file_ops entry whose access is `rw` in the agent's config. Resolving happens after canonicalizing symlinks, so `..` traversal and symlink-escape are rejected. You cannot move data out of a writable subtree into a location the operator didn't declare.

sentinel_move

Read the contents of a file on the target host. The path must fall under one of the agent's configured `file_ops.allowed_read_paths` — directories like /etc/nginx, /var/log, /opt, etc. that the host's operator has chosen to expose. Paths outside that list, or path-traversal attempts via `..`, are rejected with path_not_allowed.

sentinel_read

Reassemble all chunks into the target file. If `sha256` is provided, the agent verifies the assembled file matches it. Cleans up temp data on success.

sentinel_upload_complete

Remove the label attached to a host. The host_id is unaffected; only the alias is forgotten. Returns {"ok": true, "removed": bool}.

sentinel_remove_host_label

Restart an allowed service through SentinelX.

sentinel_restart

Run a one-off bash or python3 script on the connected host. The script content is written to a temporary workdir, executed, and (by default) cleaned up afterward. Set cleanup=False to keep the workdir for debugging — its path is returned in the response.

sentinel_script_run

Execute a command through SentinelX (must be in the allowed commands list).

sentinel_exec

Recursive content search across a directory subtree. Like ripgrep, but constrained by the file_ops allowlist and returns structured matches. Always skips binary files (heuristic: first 8KB contains NUL) and noise directories.

sentinel_search

Send a text message to a Telegram chat using a saved bot. The target chat is taken from the integration's stored configuration (`metadata.default_chat_id`), set by the authenticated user via the dashboard. This tool deliberately does NOT accept a chat_id parameter — the LLM cannot redirect messages to chats it picks. If you need to reach different chats with the same bot token, create one integration per target chat in the dashboard. Use this for operational notifications: "deploy finished", "backup failed", "container unhealthy", "user requested this summary". It is NOT a chat interface — the bot does not receive replies, and there is no inbound message handling.

telegram_send_message

Send a transactional or operational email via Resend. Use this for emails that need to land prolijo: deploy reports, backup summaries, certificate-expiry notices, weekly digests, invoices. For quick alerts where formality doesn't matter, telegram_send_message is faster to consume. The sending address (`from_address`) defaults to the integration's configured `metadata.default_from`. You can override it if the integration's API key has access to multiple verified domains and a particular send needs a specific one — but the domain MUST be verified in the Resend account this API key belongs to. The recipient list (`to`) is always passed in by the caller because email is, by nature, "send to whoever needs to read this." Unlike Telegram (where the bot has a small fixed set of reachable chats), email targets are open-world. At least one of `html` and `text` must be provided. If both are, Resend sends a multipart email and the client picks. Plain-text fallback is always good practice.

resend_send_email

Designate `host_id` as the default target when host_id is omitted. After calling this, any tool that takes a `host_id` parameter will, if not given one explicitly, route to this host. Useful when you have multiple hosts connected and almost always work with one of them. The host_id must be the EXACT identifier (not a label or hostname). Use sentinel_list_hosts to discover available host_ids. We require the exact id deliberately — labels can be changed or removed, and hostnames can collide between hosts. The default should pin to a specific, stable identity. A default that points to a host which later disconnects is NOT an error at set-time; resolve_session will just fall back to ambiguous_host with a clear "your default is offline" message when the next tool call happens. To switch defaults, just call this again with the new host_id. To remove the default entirely, use sentinel_clear_default_host. Returns: On success: {"ok": True, "host_id": "<id>", "is_connected": bool}. The is_connected flag tells you whether your new default is actually online right now — useful feedback if you pinned a host that's currently offline.

sentinel_set_default_host

Attach a human-friendly label (alias) to one of the user's hosts. The label can then be passed in any tool's `host_id` parameter as a convenient alternative to the long host_id. Labels are also surfaced in `sentinel_list_hosts` output.

sentinel_set_host_label

Get SentinelX internal state.

sentinel_state

Get the help section exposed by SentinelX capabilities.

sentinel_help

Get SentinelX capabilities, including allowed commands and rich service definitions.

sentinel_capabilities

Stage one role file for an edit upload session. Provide exactly one of `content` (utf-8 text) or `content_base64` (binary). `role` must be 'old' or 'new'. Defaults filename to <role>.txt.

sentinel_edit_upload_file

Partially update an existing DNS record. Change only the fields you pass; everything else stays as it was. This is a PATCH operation: omitted fields are left untouched. This is the safe semantic — "change proxied to true, leave the rest alone" — that matches how users think about edits. Use cloudflare_dns_list_records first to get the record_id. NOTE on TTL: if you set proxied=True (or the record is already proxied), Cloudflare will force ttl=1 even if you pass another value. To change ttl freely, the record must be non-proxied. To change the record's type or name (e.g. A -> CNAME), delete the record and create a new one — there's no in-place type change.

cloudflare_dns_update_record

Send one chunk of a chunked upload. `index` is 0-based; chunks can be sent out of order — the agent reassembles by index when complete is called.

sentinel_upload_chunk

Upload a file to the connected host's upload base directory. Provide exactly one of: - `content_base64`: file content inlined as base64 - `file_url`: an http(s) URL the agent will fetch `target_path` is relative to the configured upload base on the host (path traversal is rejected). Set overwrite=True to replace existing files.

sentinel_upload_file

Execute a supported service action through SentinelX. Supported actions: start, stop, restart, reload, status, is-active, is-enabled.

sentinel_service