EditorOps

DevOps automation for your code editor. Save time and eliminate context switches. Start automating your development workflows—right inside your code editor.

⚡ Switch Slack to Do Not Disturb when in flow

⚡ Set a custom Slack status when your editor is focused

⚡ Play your most productive Spotify playlist when in flow

⚡ And much more...

Getting Started

Make your code editor work for you. With EditorOps, we envision a smarter code editor that helps you make daily work faster, more efficient, and more enjoyable.

Install the EditorOps extension. Get the latest EditorOps extension from the Visual Studio Code marketplace. It's fast and easy.
Automate your workflows. Choose your triggers and actions to control your workflows. Get started with automations for Slack, Google Calendar, and more.
Build custom workflows. Trigger custom actions by writing your own scripts. Explore and remix workflows from the community.

Creating Workflows

To create your first workflow, select the EditorOps icon in the sidebar. Follow the instructions in your editor to create a Software account to get started. Once you've created an account, return to your code editor and you will be signed into your new account.

You can create automations using built-in templates, which allow you to get started using popular workflows. Currently, there are two templates available. Flow Mode Enabled turns on Slack's Do Not Disturb and sets a custom status message when you're in flow. Flow Mode Disabled resets these Slack settings.

You can also design your own workflows by selecting triggers and actions. To create a custom workflow from scratch, click + Add in the EditorOps sidebar.

Triggers

Select a trigger

First, select a trigger for your automation. Triggers are events that start an automation.

	Trigger	Description	Dependencies
🟣	Auto Flow Mode	Automatically detects when you enter or leave flow state based on coding activity.	Code Time
📅	Calendar Focus Block	Detects when you enter or leave a protected focus block on your calendar. Create focus blocks in the web app.	Google Calendar, Microsoft Outlook
⏱️	Cron	Write a custom cron expression to fire at specific times.

Actions

Next, select actions for your automation. Actions are events that happen in response to a trigger. Each trigger can have multiple actions.

Select a trigger

	Action	Description	Dependencies
🔕	Slack Do Not Disturb	Enable or disable Slack's Do Not Disturb for a custom duration.	Slack
💬	Slack Status Message	Set your Slack status with a custom message.	Slack
📁	Custom Script	Run a custom script. Enter a command or select a file.
🌐	HTTP Request	Make a POST or GET request to a URL.

After creating your workflow with triggers and actions, you will be able to see all your active automations in the EditorOps sidebar. When you click on an automation, you can update, rename, or delete it.

Integrations

Start automating your workflows by connecting your favorite tools. Discover new and remarkable ways to improve your daily work with integrations to Google Calendar, Microsoft Outlook, Slack, and more.

Slack: Connect a Slack workspace to update your Slack status and toggle Do Not Disturb on or off.
Code Time: Automatically detect when you're in flow based on your coding activity. Protect high velocity coding sessions by automating away distractions.
Google Calendar and Microsoft Outlook: Create protected focus blocks on your calendar using the Software web app. Trigger workflows when you enter or exit focus time.

Community Workflows

Explore awesome workflows built by our community of over 150,000 developers.

	Action	Description	Language
	Play LoFi Beats on Spotify	Start playing Spotify's most popular LoFi playlist.	AppleScript

Enjoying EditorOps? Let us know how it's going by tweeting or following us at @software_hq.

Have any questions? Create an issue in the EditorOps project on GitHub or send us an email at support@software.com and we'll get back to you as soon as we can.

It’s Safe, Secure, and Free

We never access your code: We do not read, transmit, or store source code. We only provide metrics about programming and automate workflows from those metrics, and we make it easy to see the data we collect. You can learn more about how we secure your data on our security page.

Your data is private: We will never share your individually identifiable data with anyone.

Free for you, forever: We provide 90 days of data history for free, forever. We provide premium plans for advanced features and historical data access.

Editor Ops also collects basic usage metrics to help us make informed decisions about our roadmap.

Data collected and purpose | Data Collected | Purpose of Data | | -------------- | --------------- | | Local Timezone | Applying time zones to aggregate metrics so that daily values are accurate | | Hostname | Used for de-duplicating accounts and linking multiple installations together under same login. Hostname is hashed before usage | | File open, save, close events | These events are used to capture general activity within the editor and extend code time sessions | | Editor focus / unfocus | These events are used to capture general activity within the editor and extend code time sessions | | Document change events | These events are used to characterize what types of changes are being made to a document. CONTENT OF A DOCUMENT IS NEVER STORED OR TRANSMITTED | | Project directory | Used to segment activity and Code Time across projects | | Git Repo Name | Used to segment activity and Code Time across git repos (Can be turned off in settings) | | File name | Used to segment activity and Code Time across file names (File names are one-way hashed before use) |

More details here

Editor Ops

Software