Skip to main content

​
Overview

Intuned allows you to develop your projects using the online IDE or locally using the CLI. This guide focuses on the online IDE. You should use the online IDE when:
  • You want zero setup—just open your browser and start coding.
  • You want embedded AI assistance to build and edit automations.
  • You want Selector Agent to generate selectors from the live page.
  • You need platform-native workflows like AuthSessions and browser-based debugging.
  • You’re working solo on smaller projects.
For the CLI approach, see Local development.

​
Create a project

To create a project that runs in the Online IDE:
  1. Go to app.intuned.io/projects
  2. Select Create Project
  3. Choose your language (TypeScript or Python)
  4. Select a template or start from scratch
  5. Name your project
  6. Ensure “Hosted project” is selected as the project type (not Connected project)
  7. Select Create and Open
Create project dialog with IDE type selected
Your new Hosted project opens immediately in the browser with all components ready to use.

​
IDE interface overview

Intuned IDE layout
The Online IDE includes these components:

​
1. File Explorer (Top Left Sidebar)

The file explorer displays your project’s folder structure: 
//api/
//└── sample.ts          # Your automation API files
//Intuned.json           # Project configuration
//package.json           # Package dependencies

​
2. Changes to deploy (Bottom Left Sidebar)

Shows changes that will be included in your next deployment.

​
3. Code Editor (center panel)

A VS Code-based editor with syntax highlighting, IntelliSense, familiar keyboard shortcuts, embedded AI assistance for project edits, and inline code suggestions.

​
4. Run Controls (Top Center Toolbar)

Select an API, configure parameters, and start execution with the Play button.

​
5. Terminal (Bottom panel)

Displays execution logs, traces, and output from your automation runs:
  • OUTPUT tab - Shows VS Code extension logs and messages
  • TERMINAL tab - Shows command output such as yarn install or intuned run api
The terminal shows what’s happening during execution—essential for debugging.
You can’t use the terminal to run arbitrary commands. It only displays output from IDE-executed commands.

​
6. Browser Panel (Right Panel)

A live browser view that shows your automation executing in real-time. Watch exactly what your code does and debug UI issues immediately.

​
7. Browser Controls (Above Browser Panel)

  • Restart Browser - Restarts the browser instance
  • Clipboard - Copy text from the browser to your local clipboard
  • DevTools - Opens browser dev tools for debugging
  • Selector Agent - Generates selectors for elements using the live page context

​
8. View Controls + Deploy Button (Top Right Toolbar)

  • Toggle Sidebar - Show/hide the left sidebar
  • Toggle Terminal - Show/hide the bottom terminal panel
  • Toggle Browser Panel - Show/hide the right browser panel
  • Theme selector - Switch between light, dark, and system themes
  • Deploy - Triggers project deployment

​
AI in the IDE

The Online IDE includes embedded AI assistance for building and maintaining automations without leaving the editor.
AI chat panel in the Online IDE

​
What it can do

  • Answer browser automation questions in the context of your current project
  • Edit the current project
  • Generate selectors from live page context through Selector Agent
  • Provide inline code suggestions while you type

​
Selector Agent

Selector Agent is the selector-focused part of AI in the IDE. It uses the live browser view and the current project context to generate code-ready selectors for the automation you’re building. To use Selector Agent, click the Selector Agent icon in the browser controls toolbar, then click the element you want to target on the live page. Selector Agent analyzes the page context and generates a reliable selector for your automation code.
Selector Agent element selection mode in the browser panel
Use Selector Agent when element targeting is unclear, the DOM is noisy, or you want a faster path than manually inspecting markup and guessing selectors.

​
Availability and credits

AI in the IDE is available only for Hosted projects. These features consume AI credits, so if credits are exhausted the AI tools in the editor are unavailable until credits are available again.

​
Development workflow

APIs in the api/ folder become callable endpoints when deployed. Build them by editing code manually or with AI in the IDE, use Selector Agent when you need help targeting elements on the live page, then use the run controls to test any API with parameters before deploying. The browser panel shows your automation executing in real-time, so you can verify behavior visually and iterate quickly.
Running an API in the IDE with real-time browser view

​
Draft vs deployed versions

When developing in the IDE, your project exists in two states:
  • Draft version: The code currently in your IDE editor (not yet live)
  • Deployed version: The code running in production (available via API endpoints)
The Changes to deploy panel shows what changed between draft and deployed versions.

​
How deployment works

When you select Deploy, we build and validate your code, run health checks, and deploy if all checks pass. Only the deployed version is accessible via Standalone Run APIs and Jobs—draft changes don’t affect production until you deploy again.

​
Branches and checkpoints

Your project’s shared draft is called Main. Intuned gives you two tools for managing change on top of it:
  • Branches are isolated copies of Main where work happens before merge.
  • Checkpoints are saved project states created automatically when Intuned persists important code changes.
The main use case for branches is agent work. Intuned Agent uses branches to keep its changes isolated until you review and merge them. You can also create branches yourself when you want to make a change without editing Main directly.

​
Branches

Branches are part of the Intuned workflow for IDE projects. They are not Git branches.

​
What branches are for

Use a branch when you want to:
  • keep work isolated from Main
  • review a change set before merging it
  • let the agent work on a project without editing the shared draft directly
  • organize active work separately from completed work
Project Home showing the Branches section with the create branch action

​
How to create a branch

Branches are managed from Project Home, the project overview page outside the editor.
  1. Open the project in Project Home
  2. In the Branches panel, select Create Branch
  3. Enter a branch name
  4. Open the branch in the IDE
New branches start from the current state of Main.

​
How to view a branch

You can view branches in two places:
  • Project Home shows the full list of branches, their status, and actions such as open, merge, and archive
  • The IDE shows which branch you are currently editing
From the Branches panel, open any branch in the IDE to continue working on it.

​
How to merge a branch

  1. Make the changes on the branch
  2. Mark the branch as Ready when the change set is ready for review
  3. Return to Project Home
  4. In the Branches panel, merge the branch back into Main
Intuned checks the current project state before merging. If a linked agent session is still in progress, merge may be temporarily unavailable until that session reaches a mergeable state.

​
Branch states

The Branches panel and the IDE use these states:
StateWhat it means
In ProgressWork is still happening on the branch.
ReadyThe branch is ready to be merged into Main.
MergedThe branch changes have already been merged into Main.
ArchivedThe branch is no longer active, but it remains part of project history.
DeployedChanges from the branch have been included in a deployment.
When the agent handles deployment, you may also see Auto-deployed as the user-facing label. When the agent is involved, Project Home can show automation badges such as:
  • Auto-created
  • Auto-merged
  • Auto-deployed
These badges help you understand which parts of the branch lifecycle were handled by the agent.

​
Checkpoints

Checkpoints are created automatically when Intuned saves important project states. They are part of project history, not separate working spaces.

​
Which checkpoints you will usually see

You do not create checkpoints manually in the current workflow described here. Intuned creates them automatically when important project states are saved. Checkpoint-related activity entries can appear in different forms depending on what was saved. Common examples include:
  • descriptive notes attached to a saved change, such as Adding comments to the books scraper
  • automatic Pre-merge checkpoint entries created before a branch is merged into Main
  • Merged branch or Deployed to production entries when a merge or deployment is saved without a more specific note
These checkpoints record that code was saved at an important milestone.

​
How to view checkpoints

Open Project Home and check the Activity panel. This is where checkpoint-related history appears. The Activity panel shows:
  • what happened
  • who or what triggered it
  • when the code was saved
This makes it easy to understand how the project changed over time across both human and agent work.
Project Home activity panel showing checkpoint-related entries
Checkpoints in the current product are viewed through project history in the Activity panel. They are not a replacement for Git history or a standalone checkpoint manager.

​
Work with AuthSessions

For projects that require authentication (logging into websites before automation or persisting browser sessions between runs), you can enable AuthSessions in your Hosted project. See AuthSessions for details.

​
Enabling AuthSessions

  1. Open Intuned.json in your project
  2. Set "authSessions": true in the configuration
Enabling AuthSessions in Intuned.json
This creates special authentication files in your project:
  • auth-sessions/create - Handles the login/authentication process
  • auth-sessions/check - Validates if the session is still valid

​
Testing authenticated APIs

Before running APIs that require authentication:
  1. Create an AuthSession by running auth-sessions/create
  2. Run your API - it will now use the newly created AuthSession
  3. If you have multiple AuthSessions, select which one to use from the dropdown in the top toolbar
Creating and validating AuthSessions in the IDE
You can create AuthSessions two ways:
  • Credentials-based: Use auth-sessions/create to create and save a browser session
  • Recorder-based: Record yourself logging in via the browser panel, then save the session when done

​
Deploy your project

When you’re ready to make your automation available as a live API:
  1. Select Deploy in the top-right toolbar
  2. Watch the live deployment logs as your project is built and deployed
  3. Wait for “Ready” status indicating successful deployment
If deployment fails, the IDE will show error logs. Fix the issues in your code and try deploying again. Your previous deployed version remains active until a successful deployment completes.
After deployment, all APIs become callable endpoints. Trigger runs via Jobs or API calls.

​
Intuned settings file (Intuned.json)

Hosted projects use Intuned.json for configuration, but unlike Connected projects, you have a controlled UI to modify settings. Open Intuned.json in the file explorer to view and edit settings. See the Intuned settings file for details on each configuration value.
Intuned.json configuration in the IDE

​
Best practices

Always run your APIs multiple times in the IDE with different parameters to ensure they work correctly. Use the real-time browser view to catch issues early.
If your automation requires logging in, enable AuthSessions and test the authentication flow in the IDE before deployment. Ensure auth-sessions/check passes consistently and is performant.
Use Intuned Agent to create and edit Hosted projects through natural language. The Agent can only work with Hosted projects, not Connected projects.

​
Limitations

No Git integration: The IDE doesn’t integrate with Git, but you have full versioning and deployment history built in. For Git workflows, use the Local CLI. Single developer only: Multiple people cannot make edits on the same Hosted project simultaneously. No local IDE choice: You must use Intuned’s web-based editor. If you prefer VS Code, JetBrains, or other IDEs, use the CLI approach. AI in the IDE is available only for Hosted projects: Selector Agent and the rest of the built-in AI tools are not available in Connected projects.

​
FAQs

Not directly. Hosted and Connected projects have different structures. You’ll need to create a new project of the desired type and copy your code manually.
Your draft remains in the IDE. The deployed version continues running unchanged. You can keep drafts indefinitely without deploying.
No. AI in the IDE and Selector Agent are available only in Hosted projects. If you develop locally with the CLI, use your own editor, Git workflow, and AI tools.

​
When to use IDE vs CLI

FeatureOnline IDELocal CLI
SetupZero setup, browser-basedRequires Python or Node runtime and Intuned CLI
Use caseUse Intuned Agent to build and edit scrapers
Use platform-specific features like stealth and captcha solving
Quick prototyping		Integrating your own CI/CD with version control and predefined team workflows
Version controlNo Git integration
Use built-in deployment tracking and history management		Full Git workflow that works with your team and your own repo
CollaborationSingle developer (no concurrent editing)Multiple developers with version control
IDE choiceIntuned’s web-based editorUse your preferred IDE (VS Code, JetBrains, etc.)

Local development CLI

Develop locally with your own IDE and Git workflow

Intuned Agent

AI agent that builds and maintains browser automations

AuthSessions

Build authenticated automations

How the platform works

Understand Intuned’s architecture and execution model