Editor User Guide


The Extend Editor allows you to see your console.log() output. You can use these logs to help with your development of tasks.

Logs in the Editor

Click the “Logs” button in the top right corner of the editor, and the logs panel will pop out in the bottom of the editor. The logs will show running information about the extension and are searchable. The logs only accumulate while open, so before running an extension, make sure to open the logs panel.


Below is an overview of the various parts of the log panel:

1: When dumping data to logs, the amount of it could quickly get overwhelming to sift through. The Search Bar allows you to search the currently displayed log output for particular terms, error messages, etc.

Tip: Logs in the Extend editor are container specific, rather than task specific, so the logs will be for all of your tasks as opposed to just the current one. However, if you add the extension name to your logs, you can then filter logs using the search bar to only show log entries from the current extension!

2: The Autoscroll option, when enabled, keeps the logs panel at the latest log entry - it autoscrolls as new log items are added to the list. This allows you to be seeing the most recent log messages at any given time.

3: In the top right corner of the logs panel, there is a Clear button (a trash can icon) which can clear the current history of the logs panel. This is useful, for example, when debugging. Once changes have been made, the logs panel can be wiped to a clean slate before starting a new attempt at running the task.