WINDOWS · .NET 10 · AGPL-3.0

Cronopus

Schedule and run tasks locally or on remote nodes, manage ZennoPoster, ZennoBrowser and ShardX, inspect XML, HTTP archives and SQL — in one dashboard. The local panel uses localhost; Remote Tasker connects other instances over HTTPS.

The windowed build requires the WebView2 Runtime. Choose SQLite or PostgreSQL in Config. Windows 10 or 11, x64. Building from source also needs the .NET 10 SDK.

>_[ fig. 1 — tasker ]↗
01

Schedules without someone else's runner

Python, Node, TypeScript, npm, executables, shell scripts, C# and ZennoPoster XML. Schedules, payload forms, bulk controls and output. Remote Tasker manages another instance over HTTPS, uploads scripts and retrieves remote logs on demand.

02

ZennoPoster workers on your LAN

Worker state, task queue, stop and restart — every machine at once, from a single table. The shared log history and the HTTP traffic window open from there too.

03

Tools within reach

ZennoBrowser and ShardX profiles, ZennoPoster XML editing and debugging, an XML tree, HAR replay, JSON, SQLite editing, read-only PostgreSQL queries, clipboard templates and Windows RAM/commit diagnostics.

04

Documentation inside the app

The same vault this site is built from. Press Alt+H and it opens — no internet, no extra tabs.

05

Native MCP for agents

Cronopus.exe --mcp connects an agent to the running application: tasks, schedules, output and saved Remote Tasker connections. MCP discovers the actual port, checks revisions on updates and provides built-in documentation.

// FIRST RUN
✓
Launchno elevation needed

A localhost prefix needs neither a URL reservation nor running as administrator.

✓
SQLite or PostgreSQLchoose in Config

Use a SQLite file or a PostgreSQL connection string. Required tables are created automatically. Environment checks and installation actions are on System.

ZennoBrowser / ShardXoptional

Configure the local address and token in Config → Browsers API, then choose the provider on Browser.

Remote Taskeroptional

On the server, open Config → Remote Tasker, enable HTTPS and create a key. Paste the connection code into Tasker → + New connection… on your machine.

Panels

The dock opens the panels below; available keyboard shortcuts are shown on each card. Config → Interface controls themes, dock position and visible pages.

Tasker

Alt+1

Control another instance by IP: Remote Tasker. The node selector chooses Local or a saved remote connection; + New connection… accepts a connection code. Task settings and commands apply to the selected node. Native editor and terminal actions remain local. The Output and Traffic descriptions below refer to Local; remote output uses explicit Refresh (↺) / Older / Observe controls, and Traffic is local-only.

List
Tasks are read from the schedules table. The list shows the name, the state and the main run parameters. Within each group, running tasks and enabled schedules that are neither paused nor deferred come first. The remaining tasks follow; each category is sorted alphabetically by name. Running tasks stay in the first category even if their schedule is disabled. BrowserAutomationStudio XML projects use the separate BAS page (Beta), not the ZennoPoster xml executor below. Set dot-separated name grouping in Config → Interface → Tasker grouping depth.…
Editing
A task is defined by: A name, an executor, a path to a script, file or task, arguments, the enabled state, a schedule, an overlap policy, a payload. Supported executors: python, node, ts-node, npm — scripts of the matching runtimes; exe, cmd, bat, bash, ps1 — executables and shell scripts; csx — a C# script; the task list carries a compile-check button for it; xml — a ZennoPoster template: the built-in runtime plays the XML graph, and the browser is chosen on the task card. Use Ctrl+click to select several tasks and Shift+click to select a range.…
Resources
RAM and CPU appear per task and in the header total. On Windows, each instance includes its child processes, including browsers. CPU is shown as a share of the whole machine after the second sample. Cronopus's own memory is separate; in-process XML runs are marked instead of receiving an individual memory figure. Each active instance shows the memory of its entire process tree and its process count. Instance figures, task totals and header RAM use one snapshot; a task's memory equals the sum of its instances.
Schedule
The UI can build: On-demand runs, daily runs, runs on days of the week, runs on a day of the month, an interval in minutes. The result is stored in cron, interval_minutes and fixed_time.
Overlap
Skip — do not start a new instance while one is active, parallel — allow several instances up to max_threads, kill_restart — stop the active instances and start a new one.
Account for a template run
The xml executor reserves an account only when the template actually works with one: the acc0 variable is declared in the <Variables> block and mentioned somewhere else — in a step or in the own code. A declaration alone is not enough: ZennoPoster templates carry variables over from a donor project in bulk, and many of them are never read. Reservation also kicks in when the task payload explicitly sets accountTable or condition. It is skipped when the payload already carries a non-empty acc0 — the account was picked by hand.…
Max runtime
The Max runtime field in the task settings (column timeout_seconds). 0 means no limit. Once the limit passes, the run is aborted, a line about the limit goes into the output, and the run counts as a failure (last_exit = -1). How the abort happens depends on the executor: An external process (python, node, cmd, npm, …) is killed together with its process tree — a real stop, xml gets its CancellationToken cancelled. Cancellation is cooperative: it checks the token between branches, and code that never looks at the token will not stop.
Control
Available actions: Run, Stop, Restart, enable or disable the schedule, delete and duplicate, open the file or its folder, open a terminal, check and install Python and Node dependencies. Run, schedule pause/enable, Resume schedule, Restart, Interrupt and Eliminate apply to all selected tasks. Run queues the chosen count for each task; the header shows the selection count. Bulk controls continue after individual failures and collect errors into one message. Interrupt can also clear pending runs.…
Attempt counters
Reset attempts clears the successful and failed attempt counters for all selected tasks. It does not stop running instances or change their schedules.
Upload a local task
Select a local task and press ↑ Upload, choose a saved Remote Tasker server and its destination folder, then confirm. This copies the task's script file or folder, current settings, schedule and payload, and creates a task on the server. The script path is changed to the destination; run counters start at zero. An enabled schedule remains enabled and can start on the server immediately. File replacement requires confirmation. If task creation is unconfirmed after a connection failure,…
Local output
Output of the active run is streamed over SSE. Parallel instances each get their own runId. Select a thread chip to show only its lines. The selection survives subscription refreshes and incoming buffer clears for the same task, including progress-line replacements. Selecting another task resets the filter. Auto-scroll follows new output and remembers the setting. When disabled, the displayed log is frozen, including progress replacements and clear events. Enabling it again applies the bounded buffer of incoming output and scrolls to the end.
Execution
The tab shows the launch command built from the task's saved settings and payload. Passwords are masked. Saving or clearing the payload refreshes the command. Late statistics, instance and queue responses cannot replace the current task's data after switching cards.
Traffic
A task tab with traffic from trafficLog.jsonl: GET /traffic?tail=N&task_id=..., polled every 3 seconds. ZpRuntime writes it; details are in Traffic. The file rotates itself.
Payload
A payload consists of a schema and values. It can be edited, imported, exported and passed to the executor on start. Changing the script path regenerates payload fields and defaults from the new Python script. From script replaces the payload using the current script path, including an unsaved edit. Outdated parameter responses are ignored. When the path is changed, payload Save keeps edits in the draft until Settings saves the new path and payload together. Otherwise, Save and Clear persist the payload independently of unsaved Settings.…
Full documentation →

ZP7

Alt+2

ZP7 shows task state taken directly from the registered ZP node services.

Data source
Cronopus stores only the node addresses and their tokens, in the zp_nodes table. Task state is requested from each node: The token comes from the node registration line (see 02. Adding a ZennoPoster worker on the LAN) and is attached on the Cronopus side: it never reaches the browser. A node that answers 401 is marked Unauthorized in the list — paste the registration line again. The node list in the NODES window comes from GET /zp/nodes with a probe: alongside availability it carries the node's z3n7 and ZennoPoster versions, taken from GET /version.…
Task list
Filters are available by: Name, state, run mode, tags. The chosen filters are kept in the UI state.
Control
Commands go straight to the selected node: The action bar is icons only; each label lives in the tooltip: green ▶ — start — start; yellow ❚❚ — pause (the task stops but is not interrupted) — stop; red ✕ — interrupt — interrupt; node with two branches — Input Settings — set_input_settings; ± — tries: a modal with a Set/Add toggle, a value field and +1 / +10 / +100 (they edit the field; Apply sends the command) — set_tries, add_tries; Clear ✓ / ✗ — clear done / clear fails — clear_success,…
Panels
Task Detail — parameters and actions of the selected task, Logs — logs of the selected task from its node (GET /zp/log), allLogs — a modal window with the shared history from every node, with filters and sorting, traffic — a modal window with HTTP traffic from every node and from Cronopus itself, HTTP — traffic of the selected task: GET /zp/traffic?machine=...&task_id=..., polled every 3 seconds, Projects heatmap — project data from the report API.
Input Settings
⚙ Input Settings opens the project variables. Values come from the node as GET /zp/task/settings?machine=&task_id= — a base64 pair: the original InputSettings XML and the current values. Two views, switched with the button in the window footer: Form (default) — widgets by the types in the XML:. Tab — a tab; Comment — a section separator; Label — a caption with no input; Boolean — a checkbox; Number — a numeric input; DropDown, Select — a dropdown; DropDownMultiSelect — a set of checkboxes; Password — a hidden input; everything else (Text, FileName,…
Full documentation →

BAS

Beta in Cronopus 1.2.0.0: this module is still in development, is not fully tested or feature-complete, and may contain bugs. The Beta designation applies only to BAS; other Cronopus modules retain their stable status.

Run a project
1. Select Local or a saved HTTPS connection. Manage connections in Config → Remote Tasker. 2. Click New, then Choose XML. Local opens the Windows file dialog; remote opens the selected node's file browser, showing directories and XML files. Choosing a file fills its path and suggests a name. You can change the name before saving. Cancel leaves the current selection unchanged. 3. Resources load automatically from the XML on the selected node. From XML refreshes the form after external source edits.…
Engine and process lifecycle
The first run downloads the unprotected engine for the XML's EngineVersion over HTTPS and verifies its publisher-provided SHA-1 checksum. The archive and pristine engine are shared by version on that node. Per-project runtime folders isolate mutable settings; large executable binaries use NTFS hard links where supported, with copy fallback. Runtime cloning also preserves empty BAS service directories. Older runtime layouts are repaired when prepared again, without another download or replacement of their settings.…
Results and network uncertainty
Run acknowledges submission, not completion. A successful process exit alone is insufficient: Cronopus requires a native execution report with a successful final message and no failures. Exit code zero without a report is reported as unconfirmed execution, not success. Remote execution reuses Remote Tasker HTTPS, certificate pins, keys, revocation and operation journaling. If a mutation reply is lost, Check command reads the original journal entry without sending the command again.…
C# integration
BasControlClient: local XML preparation, owned process lifecycle, log tailing and native report verification, BasXmlProject: safe XML parsing, resource validation and source preservation, BasControlService: saved projects, revisions, execution states, cancellation and bounded history, BridgeHost.InvokeBasAsync: journaled integration under /bridge/v1/bas/; the local page uses guarded /bridge-local/ routes.
Verification
The normal suite uses isolated storage and fake execution over real certificate-pinned HTTPS. Live verification executes the harmless XML smoke fixture in an actual BAS 31.1.0 engine and checks its native report and unchanged source. Set CRONOPUS_BAS_TEST_ENGINE to an existing test engine executable to avoid a fresh download. For browser acceptance, start the suite with --serve, then run rtk python tests/bas_browser.py <BAS_BROWSER_URL>. The test server prints its actual URL, preferring port 39761.
Full documentation →

Browser

Alt+3

Browser manages anti-detect browser profiles. The switch in the header picks which browser to work with: ZennoBrowser or ShardX. The choice is kept in the browser.

Connection
The address and token come from the Browsers API section of Config: ZennoBrowser — BrowsersApi.ZennoBrowser — http://localhost:8160 — Api-Token header; ShardX — BrowsersApi.ShardX — http://127.0.0.1:40325 — Authorization: Bearer <token>. The token never reaches the page: the Cronopus server adds it while proxying.
Profiles
The profile table shows name, folder, proxy, tags (ZennoBrowser only), status and last start time. A running profile shows its PID and uptime instead of the time. + New profile — create a profile: name, platform, folder, proxy, tags. ZennoBrowser: Auto (host OS), Windows 10 or Windows 11. ShardX: Windows, macOS or Linux; a fresh fingerprint comes from /fingerprint/new/{platform}. ShardX accepts a new folder name typed in. ZennoBrowser's built-in "without folder" folders are hidden from the form, cloud folders are marked (cloud).…
Proxies
Stored proxies. ZennoBrowser: name, URI, check status, check time. ShardX: name, kind://host:port, country, id.
Threads
ZennoBrowser only: busy threads, freed one by one or all at once.
ShardX specifics
Verified on ShardX Launcher 2.0.3: Times arrive as @<unix-seconds>, not ISO, after stop a profile stays in /running for about 7 seconds, so the page. re-reads the list until it is gone (15 seconds at most); A new proxy string is checked for about 10 seconds, but it is bound even when. it does not work; Deleted profiles go to the launcher's trash.
ZennoBrowser specifics
A new proxy string is matched against stored proxies by exact URI; when none. matches, it is created with the name host:port; Proxy changes go through update_proxy_bulk, which touches only the proxy, a profile without a folder is stored locally in "Profiles without folder".
Full documentation →

HAR

The HAR page views HTTP archives in the HAR format and replays requests from them.

Data source
The file is opened locally: the page reads log.entries and parses it in the browser. The page itself has no server routes. Records can also be added by importing cURL, with no file at all.
Storage
The loaded archive is kept in IndexedDB and survives a page reload. Clear HAR wipes both the list and the stored copy. HAR records never reach the Cronopus database.
List
Filters are available by: Method, status, URL, project. A limit on how many records are shown is set separately. Refresh re-applies the filters to data already loaded and never touches the network. Reset clears the filters.
Replay
A selected request is sent through the same replay listener the Traffic window uses — POST /http-replay. Method and URL can be changed before sending, and the response can be copied.
Code
For a selected record the page generates stubs: API Skeleton, API Example, HttpClient, ZP7, Hybrid, Python, TypeScript, cURL.
Full documentation →

zpXml

The /zpxml.html page renders a ZennoPoster XML template as an executable graph, supports structural editing, and runs an embedded debugging session.

Open and inspect
The open… button uses the system dialog and keeps the full template path. The runtime needs it to resolve .env, shared code, and other project files. The graph supports zooming, panning, label/ID search, and switching between the template canvas coordinates and a vertical layout. The step panel shows the action type, parameters, code, caption, flags and transitions. Template settings expose project InputSettings and profile data.
Edit
In edit mode you can: Change branch parameters, code, captions, flags and case keys, reorder branches or move them between blocks, extract a branch into a new block, delete a branch while redirecting incoming transitions, set transitions by dragging their ports, move blocks on the canvas, undo and redo with Ctrl+Z and Ctrl+Y. The page warns before leaving with unsaved changes. save .xml downloads the edited document with its original XML declaration and encoding.
Debug
start creates one server-side session with a browser. step, run, pause, run-to-branch, and stop then control execution. The current branch, variables, profile and log update over SSE. The graph follows execution only when the current branch has moved outside the visible area. Debugging uses the /dbg/* routes. One session can run in the application at a time, and it is released automatically after 10 minutes of inactivity.
Full documentation →

XML

Alt+9

The /xml.html page opens arbitrary XML as a tree.

Input
Paste XML into the editor, drop a file on the page, or choose one through the system dialog. File encoding is detected from the BOM, including UTF-16 ZennoPoster templates. Format formats the source and Parse rebuilds the tree.
Tree
Search filters tags, attributes and text, depth presets 1, 2, 3 and 5 provide quick expansion levels, individual nodes or the whole tree can be expanded and collapsed, virtual scrolling avoids creating a DOM element for every row in a large file, the source/tree split can be dragged and is stored locally. The page is available as XML in the dock and through Alt+9.
Full documentation →

JSON

Alt+6

JSON is a local JSON viewer and editor.

Working with the document
Paste JSON, format it, walk the value tree, search, collapse branches, copy a value or its path, filter fields.
Security badges
The interface marks values that look like secrets or sensitive data. This is a heuristic highlight, not a security check.
Replay
The document can be used as the body when preparing an HTTP replay.
Full documentation →

Text

Alt+7

The Text page holds local text transforms.

Tools
URL encode/decode, Base64 encode/decode, C# string escaping, JSON string escaping. Everything runs in the browser and needs no database.
Full documentation →

Clips

Alt+C

Clips stores named text templates for quick copying.

Capabilities
Browse the template tree, select and copy content, create and edit entries, store a path, a title and the text.
Storage
The data lives in the clips table.
Full documentation →

SQL

Alt+-

SQL is a separate panel for SQLite files and PostgreSQL connections. Choose the database type in the header. The page keeps its existing /?page=sqlite address and does not change the main Cronopus database.

SQLite
Open a database file, list its tables, run a query, change a value, delete a row. SQLite works on the selected file passed in the viewer API request. Cell editing and row deletion are available only for SQLite.
PostgreSQL
Select PostgreSQL, enter a connection string and press Connect. The panel lists accessible tables and views with their schema names. Selecting a table queries its first 1000 rows; use the SQL field to run your own query. SELECT and WITH queries returning a read-only result are supported. Queries run inside a read-only transaction. Results are capped at 10,000 rows; the panel reports truncation. Use WHERE or LIMIT to narrow large queries. Connection timeout is 10 seconds, command timeout is 30 seconds, and the overall request timeout is 40 seconds.…
Full documentation →

System

Alt+S

System Snapshot collects a diagnostic snapshot of the current Windows system.

Refresh
Opening the page starts a capture automatically on the machine Cronopus runs on. Refresh collects current data again. The page includes the sections the backend actually managed to gather: processes, network and system data. The page data lives in memory only.
Memory allocation
The summary shows physical RAM and Windows commit. Commit includes the current allocation, limit, remaining headroom and peak since boot; paged and nonpaged kernel pools are shown alongside it. Commit usage warns at 90% and becomes critical at 97%, even when physical RAM is still available. Process groups show private allocation and resident RAM separately, summed across instances. Unreadable private-memory measurements are counted so incomplete totals remain visible. An interactive map sizes blocks by each process group's memory use.…
CPU
The CPU usage section shows current workload by process group as a map and a table with CPU_PCT. Usage is sampled over a short interval; 100% means all logical CPUs are busy. CPU_SEC is lifetime processor time, not current load. Block area shows the group's share of displayed workload, excluding idle CPU. Selecting a block lists its PIDs sorted by current CPU. Unreadable measurements are marked unavailable. Process totals can differ from system load because of kernel work, different sampling intervals and processes that exited.
Environment
The first item in the left navigation, not part of the snapshot. It lists the tools this machine has for running tasks, showing what the command, registry or connection actually returned. A check takes a few seconds, so it runs on its own only the first time the section opens; after that, use Check. A missing tool has an Install button: the installer opens in a separate console window; press Check when it finishes. An open Environment section survives Refresh and the next visit to the page.…
Diagnostic recording
On instrumented dashboard pages, Ctrl+Shift+D starts or stops recording. The recording badge also offers Report and Stop. Correlated browser and server events help separate browser waiting, server queueing and handler time, including database, scheduler-lock and console timings. Recordings are saved as JSONL in the configured logs folder's diag directory. Stopping writes a readable .txt report beside the dump. Reports include slow requests, route timings and browser stalls; SQL events keep operation and table names instead of query values.
Full documentation →

docsVault

Alt+H

docsVault renders the Markdown files of the current docs-vault.

Generation
POST /docsVault/generate?vaultPath=... reads the Markdown files and builds links from wiki references. A relative path is resolved against the application folder.
Viewing
GET /docsVault returns the last graph and the selected folder. Before the first generation an empty template opens.
Export
GET /docsVault/export downloads a standalone HTML file of the last graph built.
Full documentation →

dllGraph

Alt+G

dllGraph builds a graph of C# code from sources or from a DLL.

Input
POST /dllGraph/generate?repoPath=... accepts: A path to a single DLL, a folder of DLLs, a folder of C# sources. When reading sources, the bin and obj folders are skipped.
Result
The generated HTML is held in process memory. GET /dllGraph returns the last graph built. After a Cronopus restart the graph has to be built again.
Full documentation →

Config

Alt+0

HTTPS bridge between instances: Remote Tasker section, see Remote Tasker.

About and updates
About shows the installed version, license, source code and release notes. On Windows, automatic checks run 30 seconds after startup and every six hours; the checkbox also enables automatic downloading. Use Check for updates or Download update to prepare a release manually. The updater downloads the stable GitHub portable package and verifies its SHA-256. It extracts the new version into a separate directory. The running application, Tasker instances and MCP clients continue working. Once ready,…
Server Status
Shows: The configuration state, the database connection, the dashboard port, the log and report folders, the selected database mode. The data is loaded through GET /config/status.
Database
Two modes are supported: PostgreSQL — a single connection string field, SQLite — a path to a file. For PostgreSQL the schema comes from Search Path. The connection string can be copied with the button beside the field.
Logs & Server
Windows startup → Start with Windows launches Cronopus when the current user signs in. It is off by default and applies when configuration is saved, using the current user's Software\Microsoft\Windows\CurrentVersion\Run entry named Cronopus; administrator rights are not required. Clearing it removes that entry. The stored setting is StartupConfig.StartWithWindows and is also reconciled on dashboard startup. If registration fails while saving, the previous configuration is restored. The dashboard port and the working folders are set here.…
Browsers API
Local API address and token for two browsers: ZennoBrowser — http://localhost:8160 by default, the token is sent in the Api-Token header, ShardX — http://127.0.0.1:40325 by default, the token (the permanent JWT from the. launcher settings) is sent as Authorization: Bearer. The Browser page and xml tasks with the shardx browser mode use these settings.
Security
The jVars section stores encrypted local variables and the path to the jVars file.
Interface
The theme: Graphite, Aluminium, Hyper or Paper (Alt+T cycles through them), the screen edge for the Nav Dock (Alt+P moves it to the next edge), Dock pages — which pages the dock shows. Config cannot be removed from the. dock, otherwise the dock would offer no way back to the settings. Changes apply at once, with no save button, and affect every page. They are kept in ui-state.json next to the executable: theme, dockPosition and dockHidden, the list of hidden pages. A page added to navpath.js later shows up in the dock on its own.…
Memory Watchdog
Configured here: The root process name, whether the watchdog is on, a memory limit in MB, a check interval. The watchdog counts the memory of the root process together with its child tree. Once a non-zero limit is exceeded, the process tree is terminated.
Storage
Shows the size and the number of files in the log folder — including trafficLog.jsonl and its rotated copies. There is a single cleanup, POST /clear-all-logs, which clears the whole folder.
Import
Available imports: Proxies, EVM addresses, SOL addresses. They use POST /import/proxy and POST /import/addresses.
Full documentation →

Download 1.1.3.2

Windows 10 / 11 x64. The installer is not signed — SmartScreen will show a warning.

Installer
Shortcuts, upgrades over the previous version.
Download .exe · 97.5 MB
Portable build
Self-contained win-x64. No .NET install required.
Download .zip · 138.2 MB
Source
AGPL-3.0. Build with the .NET 10 SDK.
Open github