Cronopus v1.1.3.1

Cronopus 1.1.3.1

First release under the Cronopus name, following z3nDash 1.1.3.

• Branding: rename the application, executable, solution, assemblies and namespaces to Cronopus; replace the application icon and update page titles, setup, documentation and release announcements.

• Migration: import an existing z3nDash installation into a separate Cronopus directory on installation or first dashboard startup. Copy missing user files and saved Remote Tasker state, back up SQLite databases including committed WAL data, and relocate configured paths within the old installation. Keep the source installation intact and accept configuration property names regardless of case.

• Tasker overview: replace the summary table with interactive task maps for results and resources. Size blocks by failed/successful attempts, failure/success rate, current status, RAM or CPU; show zero and unavailable measurements separately. Retain focus and collapsed state during refreshes.

• Tasker and ZP7: share compact SVG action buttons with tooltips, accessible names, keyboard focus and dependency-installation progress. Group related actions and display the bulk-selection count separately.

• Tasker: simplify dependency actions to package editing and npm/pip installation, retain npm script selection, and reject stale asynchronous script responses after task changes. The old config.py/config.json toolbar shortcuts are removed.

• Resources: avoid the machine-wide process-tree query when no external task roots are running, while continuing to sample machine CPU and RAM.

• Process lifetime: protect newly launched external Tasker processes with a Windows Job Object so their trees terminate when the dashboard exits. Stop scheduling during shutdown and dispose the scheduler on tray exit.

• Maintenance: bundle a standalone orphan-process cleanup utility with preview by default, exact Python-script matching, an optional parent-PID filter and explicit --apply termination.

• Remote transfers: retain exception details, HRESULT and applicable native error codes for upload/transfer failures.

• Integrations: rename the Python SDK, injected environment variables, MCP discovery identity/resources and bridge-state override to Cronopus; update the associated harnesses and English/Russian documentation.

• Updates: use the renamed GitHub repository, Cronopus portable assets and executable for subsequent automatic updates.

Upgrading from z3nDash

• Download and install Cronopus manually for this transition: the z3nDash 1.1.3 updater expects the old asset and executable names. Close the old dashboard before starting Cronopus to avoid running two schedulers. Keep the old installation until the imported setup has been reviewed.

• Install into a separate directory. Discovery checks registered z3nDash installations, the default LocalAppData directory and a sibling z3nDash directory; a portable installation elsewhere needs its data moved manually. Import skips an existing destination configuration or completed-import marker.

• Change Python imports from z3ndash to cronopus; change direct Z3NDASH_* script environment references to CRONOPUS_*. Update scripts that explicitly reference the z3nDash C# namespace or assembly.

• Point MCP clients at Cronopus.exe --mcp; resource URIs now start with cronopus://. Replace custom Z3NDASH_BRIDGE_STATE_DIR overrides with CRONOPUS_BRIDGE_STATE_DIR.

• On Remote Tasker servers, open/update the firewall rule for Cronopus: the new executable has its own rule identity. Previously exported connection codes use the old product marker; export a new code from Cronopus when adding a connection.

z3nDash v1.1.3

z3nDash 1.1.3

• Updates: add an About section in Config with the installed version, update status and manual checks. Automatic updates download in the background and apply on the next startup, with an option to disable automatic downloads.
• Remote Tasker: open and edit text files on connected servers, with conflict detection when a file changes before saving; sort folders before files in the file picker.
• Tasker: move the Payload editor into the task detail tab, retaining field editing, JSON preview, import and export.
• Tasker: show machine-wide CPU and RAM usage alongside task resource totals; improve instance-row layout and stability during refreshes.
• Tasker: show pending, completed and failed schedule actions, including remote connection and timeout feedback.
• MCP: accept both parallel and queue for the Queue overlap policy and normalize saved settings to the scheduler contract.

Downloads

• z3nDash_Setup_1.1.3.exe: installer.
• z3nDash_1.1.3_portable.zip: self-contained Windows x64 build; no .NET installation required.

z3nDash v1.1.2

z3nDash 1.1.2

• MCP: add a native stdio server (z3nDash.exe --mcp) for Tasker and saved Remote Tasker connections, with typed task tools, revision-protected updates, bounded output and an optional read-only mode. Uses the running dashboard without starting another scheduler.
• Tasker: upload local tasks and their script files to connected servers; configure nested task groups from Config.
• Tasker: add attempt-counter reset and per-instance process-tree resource statistics; improve selection and refresh behavior.
• Configuration: use a default SQLite file when no path is supplied and keep dashboard pages accessible when the database is unavailable.
• Desktop: avoid a duplicate hotkey warning when another z3nDash instance already owns the shortcut.
• Documentation: include MCP client setup, an English agent contract and updated English/Russian Tasker guides.

Downloads

• z3nDash_Setup_1.1.2.exe: installer.
• z3nDash_1.1.2_portable.zip: self-contained Windows x64 build; no .NET installation required.

z3nDash v1.1.0.0

z3nDash 1.1.0.0

• Remote Tasker: manage tasks on other z3nDash nodes over HTTPS, including settings, payloads, scheduling, run/stop, pause/resume, cloning and queues.
• Connections: add nodes from Tasker, copy/import connection codes, detect the server's public IP and manage its Windows Firewall rule. Use pinned certificates and revocable access keys.
• Files: browse server folders and transfer files or directory trees with progress, cancellation, resume, SHA-256 verification and explicit overwrite confirmation.
• Remote output: load and observe bounded logs; isolate tasks, statistics and output when switching nodes or when a connection fails.
• Remove built-in AI panels, analysis endpoints and AI configuration from Tasker, JSON, SQL, System and the project editor.
• Environment: repair winget licensing when needed and report installation failures accurately.
• Documentation: add English and Russian Remote Tasker guides and update pages for the removed AI features.

Downloads

• z3nDash_Setup_1.1.0.0.exe: installer.
• z3nDash_1.1.0.0_portable.zip: self-contained Windows x64 build; no .NET installation required.

z3nDash v1.0.7

z3nDash 1.0.7

• Tasker: regenerate payload fields and defaults when changing the script path; save the new path and payload together.
• Tasker: make From script replace the payload with the current script's parameters, including unsaved Python script paths, and ignore outdated parameter responses.
• Tasker: freeze the displayed log when Auto-scroll is disabled, including progress updates and clear events; resume with a bounded buffer of new output when enabled again.

Downloads

• z3nDash_Setup_1.0.7.exe: installer.
• z3nDash_1.0.7_portable.zip: self-contained Windows x64 build; no .NET installation required.

z3nDash v1.0.6

z3nDash 1.0.6

• SQL: add read-only PostgreSQL browsing and SELECT/WITH queries alongside SQLite, with schema-aware table names, timeouts and a 10,000-row result limit.
• System: add interactive memory and sampled CPU maps with process-group and PID details.
• Tasker: show the saved launch command, preserve payload multiselect values, and report persistence failures without closing the editor.
• Tasker: keep the selected output thread during refreshes, add a remembered auto-scroll switch, and ignore stale execution statistics and queue responses.
• Desktop: keep minimized windows on the taskbar and use the tray for closing the main window or toggling it with Ctrl+Alt+Z.
• UI: keep confirmation dialogs above the payload editor and prevent backdrop dismissal after dragging outside a dialog.
• Documentation: update English and Russian SQL, System and Tasker guides; preserve the existing SQLite documentation entry.

Downloads

• z3nDash_Setup_1.0.6.exe: installer.
• z3nDash_1.0.6_portable.zip: self-contained Windows x64 build; no .NET installation required.

z3nDash v1.0.5

z3nDash 1.0.5 adds ShardX alongside ZennoBrowser, shows the resources used by
running tasks, extends Tasker's multi-selection to run controls, and separates
Windows memory allocation from physical RAM. Interface settings now have their
own Config section, and a diagnostic recorder helps trace slow dashboard actions.

Browser

The ZB page is now Browser, with a switch between ZennoBrowser and
ShardX Launcher. The selected provider is remembered.

• Create a profile with a name, platform, folder and proxy. ZennoBrowser also
  accepts tags; ShardX obtains a fresh fingerprint for Windows, macOS or Linux
  and accepts a new folder name.
• Change a profile's proxy: choose a stored proxy, enter a new one, or remove it.
  ZennoBrowser reuses an exact URI match before creating a proxy.
• Start, stop or kill profiles, stop all running profiles, and copy their CDP
  WebSocket endpoints when the provider supplies them.
• Search and filter profiles by folder and running state. ZennoBrowser keeps
  its proxy checks and thread controls; ShardX shows proxy countries and folders.
• ShardX uses its host and token from Config → Browsers API. The server adds
  Bearer authorization to /shardx/api/* requests.
• ShardX timestamps in @<unix-seconds> format are displayed as dates. After
  Stop, the page polls for up to 15 seconds while the launcher removes the
  profile from its running list.

Tasker

• RAM and CPU usage appear per task and in the header total. On Windows,
  resource usage includes each instance's child processes, including browsers.
  CPU is shown as a share of the whole machine after the second sample.
• z3nDash's own memory is separate. In-process XML runs are identified rather
  than assigned a misleading individual memory figure.
• Run, schedule pause/enable, Resume schedule, Restart and Interrupt now apply
  to all selected tasks. The header shows the selection count; Run queues the
  chosen number of runs for each task. Eliminate also follows the selection.
• Bulk run controls continue after an individual failure and collect errors
  into one message. Interrupt offers to clear pending runs as well.
• POST /tasker/run accepts optional non-empty args for that manual batch.
  They replace the saved Args in its queued runs without changing the task;
  payload flags are still added normally.
• The active-instance list stays visible between detail refreshes and fills
  the available space above the logs. The run-count field survives header
  refreshes, and stale Config/Install responses cannot add duplicate buttons.

Responsiveness and diagnostics

• External task stdout and stderr are read on dedicated background threads.
  Silent processes no longer occupy thread-pool workers needed by HTTP
  requests, database operations and scheduling.
• Ctrl+Shift+D starts or stops diagnostic recording on instrumented pages.
  The recording badge provides Report and Stop actions.
• Correlated browser/server events split a slow action into browser waiting,
  server queueing and handler time, with database, scheduler-lock and console
  timings. Sampling also records thread-pool pressure, CPU and GC pauses.
• Recordings are saved as JSONL under 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
  retain the operation and table name rather than query values.

System

• Memory allocation shows separate charts for physical RAM and Windows
  commit, including commit limit, remaining headroom, peak since boot, and
  paged/nonpaged kernel pools.
• Commit usage warns at 90% and becomes critical at 97%. Free RAM does
  not hide an almost exhausted commit limit.
• Process groups show private allocation and resident RAM side by side, summed
  across instances. Unreadable private-memory measurements are counted so
  incomplete totals are visible. The AI audit receives the same distinction.
• Environment moves from Config to System, with its own navigation entry.
  Tool checks and installation actions remain available there and run
  independently of snapshot refreshes.

Interface and clipboard

• Config → Interface controls the theme, dock edge and visible dock pages.
  Config always remains accessible in the dock.
• The four themes are Graphite, Aluminium, Hyper and Paper:
  dark/light pairs with updated surfaces, controls and log colors. Existing
  Dark and Light selections migrate to Graphite and Aluminium.
• Theme selection moves out of the dock. Alt+T still cycles themes;
  Alt+P still cycles dock positions.
• Saving one interface setting preserves the others; theme, dock position and
  visibility no longer overwrite each other's saved state.
• Clipboard selector conversion can automatically paste the result into the
  active window with Ctrl+V. Auto-paste is on by default and can be turned
  off in Config → Services. Alt-based conversion hotkeys remain usable after
  the simulated paste.

Removed and upgrading

• The Treasury page and its supporting dashboard Web3 utilities are removed.
• Browser replaces the old ZB page: use the dock or Alt+3 to open it;
  bookmarks to ?page=zb need to change to ?page=browser.
• English and Russian documentation now covers Browser, the new interface
  settings, Environment's new location, memory allocation and manual-run args.

Downloads

• z3nDash_Setup_1.0.5.exe: installer
• z3nDash_1.0.5_portable.zip: portable self-contained Windows x64 build;
  no .NET installation required

z3nDash v1.0.4

z3nDash 1.0.4 passes the Tasker payload to scripts as named command-line
flags, lets Config check and install the tools scripts depend on, keeps the
dashboard reachable when the database is not, and adds process actions to
System Snapshot.

⚠ Breaking: how scripts receive the payload

Scripts no longer receive the payload as a single base64-encoded JSON argument.

• Each payload schema field becomes a flag: myField → --my-field "value".
  Values that have no schema field are not passed.
• Boolean fields are passed as a bare flag, and only when true.
• The task's own Args are kept and come first. A flag already present in
  Args wins, and the skipped payload flag is noted in the run log.
• For npm, the flags are placed after --.
• The account row lookup by condition from the __<project> table now
  applies only to xml templates. Python/JS/other scripts no longer get that
  row merged into their payload.

Scripts that decode a base64 argument need to be switched to reading
named flags (argparse, click, etc.).

Tasker payloads

• One Payload modal replaces the five separate payload buttons: values,
  schema, import and a command preview in one place.
• The schema can be filled from a Python script's argparse and click
  parameters. The script is parsed, not executed.
• Skip empty on a field: an empty value is omitted so the script uses its
  own default. Without it, an empty value is passed explicitly.
• Password fields are masked as *** in the command preview and in the
  [launch] line of the run log.
• A payload that cannot be turned into arguments stops the run with
  step=payload instead of launching with broken arguments.
• New endpoints: /tasker/script-params and /tasker/args-preview.

Task control from scripts

• A running script can list tasks, read a task's state, and pause, resume or
  defer any task by ID: GET /api/v1/tasks[?name=], GET /api/v1/tasks/{id},
  POST /api/v1/tasks/{id}/pause|resume|defer. The caller's run token is
  required, as for /api/v1/self.
• The Python SDK adds task(id), Task and list_tasks(name=None) next to
  the existing CurrentTask.

Environment setup

• Config → Overview checks Python/pip, Node/npx/ts-node, .NET SDKs and
  runtimes, dotnet-script, git and Git Bash, PowerShell 5/7, PostgreSQL
  (client, installations, services, port 5432), the connected database,
  the bundled SQLite engine, the SQLite ODBC driver, WebView2, Chrome and
  Playwright browsers, with versions, paths and probe output.
• Missing tools have an Install button that runs a predefined command
  (mostly winget) in a visible console window, so the result stays on screen.
• winget itself is installed from the official winget-cli GitHub release,
  so this works without the Microsoft Store.
• PostgreSQL opens its installer interactively, since it asks for the
  superuser password. The SQLite ODBC driver opens its download page.
• PATH is re-read from the registry, so a tool installed this way is found
  by the check and by tasks without restarting z3nDash.

Database

• An unreachable database no longer stops z3nDash from starting. It opens on
  Config, and the connection error is shown in its status.
• Database settings are tested before they are saved. A connection that fails
  is not written to the config.
• Switching the database from Config creates the tables the scheduler and
  handlers need in the new database.
• The dashboard's SQLite database now uses the bundled Microsoft.Data.Sqlite
  engine, so the system SQLite ODBC driver is no longer needed for it.
  ZennoPoster templates that use FastDb still go through ODBC and still
  need the driver.

System Snapshot

• Network tables include IPv4 and IPv6 TCP connections and UDP listeners,
  with the owning process on Windows.
• Process details show the executable path and command line.
• Process actions: terminate, show the executable in Explorer, and open it in
  System Informer (only an installed copy is detected, not a portable one).
• Long process names and addresses no longer break the table layout.

Fixes

• A maximized window stays inside the monitor's working area instead of
  extending under the taskbar.
• A duplicated task opens on the Settings tab.
• A path picked in the file dialog no longer lands in a different task when
  the selection changed while the dialog was open.
• The Schedule editor uses a more compact layout.
• English and Russian docs now cover the XML and zpXml pages, multi-select in
  Tasker, the Config side rail and the task control API.

Downloads

• z3nDash_Setup_1.0.4.exe: installer
• z3nDash_1.0.4_portable.zip: portable self-contained build; no .NET
  installation required

z3nDash v1.0.3

z3nDash 1.0.3 turns zpXml into an editor and live debugger, adds a proper
general-purpose XML viewer, brings bulk editing to Tasker, and moves the
dashboard onto one shared visual system.

zpXml editor

zpXml now opens a ZennoPoster template through the system file dialog and keeps
the real project path, so the runtime can resolve .env, shared code and other
project files.

• The template is kept as the document of record instead of being converted into
  a detached view model.
• Blocks can be moved on the canvas.
• Branches can be reordered, moved between blocks or extracted into a new block.
• Branch parameters, C# code, captions, flags and switch case keys are editable.
• Success, error and case transitions can be set or cleared by dragging their
  ports.
• Deleting a branch redirects incoming transitions to the next valid branch.
• Ctrl+Z and Ctrl+Y provide undo and redo with a 50-state history.
• Leaving with unsaved changes produces a warning.
• Save .xml preserves the original XML declaration and UTF-8/UTF-16
  encoding.
• C# branch code is highlighted with CodeMirror.
• Project Input Settings and profile data are available from the template
  settings modal.

Live XML debugger

A template can now be executed directly from the zpXml graph.

• Start, Step, Run, Pause, Run to branch and Stop control
  one server-side debug session.
• The session owns its browser and execution context instead of restarting the
  template for every step.
• The current block and branch are streamed to the page over SSE.
• Project variables, profile values and the execution log update while the
  session is running.
• The graph follows execution only when the current branch leaves the visible
  area; it no longer resets a manually positioned canvas on every step.
• Background proxy CONNECT refusals are hidden from the log without hiding a
  real branch failure.
• Idle debug sessions release their browser automatically.
• The debug API moved to /dbg/*, avoiding the existing /zp handler prefix.

XML runtime

The built-in ZennoPoster-compatible runtime covers more real template behavior.

• Added Switch, Alert and captcha branch execution.
• Added Hunt captcha solving, including canvas capture and slider interaction.
• Keyboard emulation now types the requested keys and keeps ZennoPoster macros
  out of the key-token parser.
• Mouse emulation distinguishes click, press and release instead of treating
  every action as a click.
• Navigation no longer fails when a redirect has already completed it.
• Project Input Settings seed runtime variables; an explicitly empty setting
  now clears the previous/default value.
• Generated profiles carry the browser's own user agent.
• The profile panel shows which generated properties the current browser runtime
  can and cannot apply.
• Empty screenshots and failed Hunt attempts now report one useful error instead
  of sending empty data or dumping repeated stacks.

XML viewer

The old XML converter has been replaced with a general-purpose XML viewer.

• Paste XML, drop a file or open one through the system dialog.
• UTF-8 and UTF-16 files are decoded from their BOM, including ZennoPoster
  templates.
• Format the source and inspect it as a collapsible tree.
• Search tags, attributes and text.
• Expand to a selected depth or expand/collapse the entire document.
• Virtual scrolling keeps large XML documents usable.
• The resizable source/tree split is restored on the next visit.
• XML and zpXml now have their own dock icons; XML opens with Alt+9.

Tasker

• Ctrl+click selects or removes individual tasks from the selection.
• Shift+click selects a range.
• Changes made on the Settings and Schedule tabs can be saved to every
  selected task.
• Only fields changed in the form are copied; task names remain individual.
• The Delete key removes the selected task or selection after confirmation.

Config and dashboard UI

• Config is split into eight sections: Overview, Database, Logs & Server,
  Browsers API, OmniRoute, Services, Security and Maintenance.
• The side rail replaces the previous single long Config page and remembers the
  last open section.
• Rebuilding the Config page no longer loses unsaved runtime settings.
• Tasker, ZP7, HAR, SQLite, Treasury, Clips, JSON, System, ZB, dllGraph, zpXml
  and the overlay pages now use the shared design-token scale.
• Added the Graphite theme: monochrome chrome with color reserved for state.
• Theme selection now controls both typeface and density.
• Bundled JetBrains Mono now includes Regular, Medium and Bold instead of
  synthesizing missing weights.
• The Nerd Font subset dropped from 7.26 MB to 202 KB.
• The obsolete report.html, terminal.html, zp_visualizer.html,
  base.css and components.css files were removed.

Clipboard converter fixes

• FindElementById and FindElementByName selectors are converted along with
  the existing selector forms.
• Generated HeGet calls now use the browser instance, matching HeClick and
  HeSet.

Downloads

• z3nDash_Setup.exe — installer
• z3nDash_1.0.3_portable.zip — portable self-contained build; no .NET
  installation required

z3nDash 1.0.1

Node traffic is now authorized, the ZP7 task card was rebuilt around icons, and
tasks got a hard runtime limit.

Node authorization

The z3n7 node server requires a token on every route, and z3nDash speaks it.

• The registration string printed by zpServer.zp now carries a token field.
  It is stored next to the host in zp_nodes and attached as
  Authorization: Bearer to every call — state, commands, logs, traffic and
  input settings.
• The token never reaches the browser: /zp/nodes returns only the probe result.
• A node that answers 401 is listed as Unauthorized instead of a vague
  "Unavailable", with the action that clears it.
• A registration string without a token still parses, so a node running an older
  z3n7 build keeps working.

Node versions

• The NODES list shows the z3n7 and ZennoPoster versions read from the node
  itself.
• The same data is proxied at GET /zp/version?machine=....
• An empty version means the node did not answer or runs a build without the
  route — the node itself is still treated as working.

ZP7 task card

• The action row is icons with tooltips instead of ten text buttons: Start,
  Pause (yellow — that is what stop actually does), Interrupt (red
  cross), Input settings, Tries, Clear ✓ / ✗, Execution,
  Scheduler.
• Tries collapsed into one button and a modal: a Set/Add toggle, a value field
  and +1 / +10 / +100 that edit the field. The command is sent by Apply
  only, and the modal stays open with the current count refreshed.
• BadEnd on Interrupt is a toggle instead of a checkbox.
• The Tags panel is gone from the card; tags remain a filter in the task list.

Per-task runtime limit

• New timeout_seconds column (0 — no limit), with a field in task settings
  and a row on the Execution tab.
• The guard fires once at the limit: an external process is killed together with
  its tree, an xml run has its token cancelled.
• A process killed by the limit is recorded as a failure rather than by its exit
  code, which is arbitrary for a killed tree.

Scheduler executors

• The xml executor reserves an account, but only when the template really uses
  one (acc0 declared in <Variables> and mentioned elsewhere). The account
  is released in finally on every exit — idle on success, fail otherwise.
• With no free account the run counters stay untouched instead of scoring a run
  that never happened; a missing account table is reported as a configuration
  error.
• The internal and csx-internal executors are gone. Their two tasks are now
  plain endpoints behind a Maintenance card on the Config page —
  POST /config/client-bundle and POST /config/update-templates, the latter
  taking its output folder from the request instead of a hardcoded path.
• Rows left in the database with those executors are reported explicitly instead
  of silently falling through to the python branch.

Packaging

• The installer uses x64compatible instead of the deprecated bare x64, so it
  also covers ARM64 Windows running x64 under emulation. ISCC compiles with no
  warnings.
• Satellite resource languages are no longer shipped: thirteen folders of
  translated framework messages that nothing ever read. Portable drops from
  342.4 MB to 327.0 MB on disk and from 136.3 MB to 131.8 MB zipped.

Fixes

• Config page: hint paragraphs no longer sit under a negative top margin.

Upgrading

1. Update z3n7 on every node to a build with authorization and run
   zpServer.zp again.
2. Re-add each node in ZP7 → NODES with the fresh registration string.
   Records saved by earlier versions carry no token and will show as
   Unauthorized.
3. Treat the registration string as a password — it grants full control of the node.
4. The token and timeout_seconds columns are added to an existing database on
   startup; no manual migration.
5. If you update a portable folder in place, delete the leftover empty language
   directories (de, fr, ru, …) — MSBuild removes the files but not the
   directories.

Downloads

• z3nDash_Setup.exe — installer
• z3nDash_1.0.1_portable.zip — portable build, self-contained, no .NET required