Version 1.1.72 (upcoming)

This update is a big step forward in anti-detection, multi-account automation, and developer power with the new Write JS zw API. It also brings code in no-code inputs, sticky browser profiles, and finer control over how browsers launch.

Here are some of the major highlights:

  • Anti-detection Power Mode

    TaskBots stay indistinguishable from human users and are not detected by Cloudflare and similar checks.

  • Sticky browser profiles & multi-account management Create multiple sticky profiles and share a single session across TaskBots per profile. No special multi-account browsers needed.

  • Write JS — new zw API

    Packages, state, device storage, browser control, metadata, better logging, and more.

  • New building blocks Launch Browser and Quit Browser.

  • More powerful browser launch options

    Pre-load scripts, add custom launch args, set the viewport, and launch with other Chromium-based browsers such as Brave.

  • Code in no-code inputs

    Combine text with ${…} expressions or $${…} code. Example: “Just adding a random number ${Math.random()}”.

...and much more! Dive into the full notes below. 👇

🛡️ Anti-Detection Power Mode

Power Mode is a major upgrade for undetectable automation.

  • Consistently undetected by Cloudflare, anti-bot systems, and sites with strong in-house protections (including Google services like Gmail).

  • Headless that doesn’t look headless. In Power Mode, background runs remain indistinguishable from human activity.

  • Enable in TaskBot run settings, the new Launch Browser block, or via zw.browserContext.launch in Write JS.

👤 Sticky Browser Profiles

Goodbye special browsers. With Power Mode plus sticky profiles, you can automate accounts without GoLogin, Multilogin, or Incognition. Sticky browser profiles make multi-account automation safer and simpler.

  • One account, one session — across TaskBots. Reuse the same sticky profile (cookies, storage, fingerprints) so multiple TaskBots working on the same account appear as a single, continuous session.

  • Multi-account ready. Create a dedicated sticky profile per account with separate proxies and cookies for clean isolation and easier organization.

  • Clone your regular browser profile. A practical replacement for “Run in my regular browser.” Clone your existing profile once, then use it as a sticky profile. You can re-clone or clear it any time.

📦 Write JS — New zw APIs

A major expansion of what you can do in Write JS.

✅ No breaking changes. Existing log(), delay(), setRef(), and getRef() (without zw.) still work. We recommend the new convention zw.* (e.g., zw.getRef()), but your current code continues to run.

Full reference: Write JavaScript (upcoming)

🧩 New Building Blocks

  • Launch Browser. Start a browser context with custom launch options directly from a building block.

  • Quit Browser. Cleanly close the active browser when needed, including mid-run.

🚀 More Powerful Browser Launch Options

More control in TaskBot run settings, the Launch Browser block, and the zw.browserContext.launch() in Write JS.

  • Add custom scripts. Inject scripts before any page loads.

  • Use external Chromium-based browsers (Brave, Chrome, Chromium). Note: some forks deviate from Chromium and may not work, e.g., Opera.

  • Use custom launch args (advanced).

    • ⚠️ Changing timezones, geolocation, locale, user agents, or similar can harm anti-detection. Use only if you know what you’re doing. Always test first in incognito mode before applying custom args to sticky browser profiles.

  • Window control. Disable maximize and set a specific viewport.

  • Even more options via the API. Record a full-run video (handy for scheduled/webhook runs), run from Firefox, add permissions, and more. Details: Browser Context (upcoming)

⌨️ Code Input in No-Code Blocks

Combine code and no-code in any text field within no-code building blocks.

  • Template expressions with ${…} and code blocks with $${…} let you resolve values directly in inputs.

  • Great for pulling secrets from device storage, formatting values, or doing quick API lookups—without adding a separate Write JS block.

More details: Code in Inputs

✨ Improved Features

  • Prettier JSON logs. JSON is now neatly indented in both running and persistent logs (especially useful for Write JS output).

  • More flexible logging. log()/zw.log() now accept direct values (like console.log). Structured messages with tag/status still work.

  • Longer live logs. Custom log messages (from the Log block and log() in Write JS) are not truncated in the running view. (They still truncate when saved to persistent run reports.)

⚙️ Optimizations

  • Faster, more reliable stop logic. Improved overall TaskBot stop behavior, including aborting non-writing requests mid-request when you click Stop, resulting in faster termination.

  • Smarter duplicate-run handling. Reduces accidental double starts with unknown run status.

  • Fewer DNS hiccups. Added TTL caching to smooth local DNS resolution, resulting in fewer handshake failures and timeouts.

  • More robust TaskBot start. Overhauled the start logic for resilience and reliability.

  • Cloud-run groundwork. Internal preparations for upcoming cloud execution.

  • Data sanitization on writes from custom code. Values saved via Write JS are normalized to valid Unicode (no mid-emoji slicing, even if your code slices or scrapes imperfect data).

  • Stale browser contexts. Improved reliability by recreating contexts (where possible) and adding heartbeats.

🐛 Fixes

  • Rare Google Sheets auth flow issue that prompted unnecessary manual re-authentication — fixed.

  • Autosize rendering bug that caused brief input lag in the canvas UI under certain circumstances — fixed.

  • Spintax with empty brackets (e.g., { A | B | {} }) — now resolves correctly.

  • Agent crash on a single value larger than 400-500 MB (e.g., big file buffers) — replaced with pre-load validation to avoid a full agent crash.

  • Back/forward retry bug — if loading failed, the retry could send extra forward/back actions. Fixed.

🔧 Changed Behavior (non-breaking)

  • More forgiving async handling for Write JS in the browser. Non-awaited async code continues running after the block finishes, while the TaskBot proceeds to the next block.

    • Recommendation: still await your async code for most reliable results.

🚨 Breaking Changes

  • Run in my regular browser is no longer supported due to Chrome v140. You may not have noticed issues yet if you haven’t updated Chrome. ✅ Replacement: use Clone from my regular browser profile plus a sticky browser profile.

  • The Upload File building block now enforces a 390 MB limit. Previously, files up to about 500 MB could sometimes work; with validation, these are now blocked. This safety limit prevents Desktop Agent crashes caused by a single upload over roughly 400 to 500 MB. ✅ This limit does not apply to downloads — you can still download files of any size, including multi-gigabyte files.

  • The Power Mode blocks IP-leak vectors to prevent real-IP exposure when using proxies. Side effect: browser-based screen sharing (Zoom, Google Meet, etc.) may not work when automated in Power Mode. ✅ Workaround: Disable Power Mode for those workflows.

PreviousVersion 1.1.71

Last updated

Was this helpful?