Current User & Developer Guide

OnlineAIIDE Documentation

OnlineAIIDE is a browser-based development platform that combines a modern code editor, integrated terminal, source control, build and debug workflows, multi-provider AI assistance, authentication, billing, and deployment-ready project tooling in one workspace. This guide is intended for end users evaluating the IDE, teams onboarding new developers, and contributors working inside the repository.

Use this page as the main handbook for day-to-day usage: how to open the right explorer for your workspace, configure runtimes and AI providers, run tests and deployments, understand quotas and billing, and find the correct services or runbooks when extending the platform.

Getting startedSign in, open a workspace, and learn the IDE surface quickly. Core workflowsEditor, explorers, AI, source control, runtime, tests, deploy, and debug. Plans, billing, and quotasUnderstand usage counters, upgrades, and payment options. Developer guideMonorepo layout, services, runbooks, and local validation.

Quick navigation

Who this guide is forUsers, admins, and contributors. First session walkthroughGo from launch to first run. Feature handbookHow to use editor, AI, run, build, and debug. Accounts and preferencesLogin, profile, AI settings, and personalization. Subscription detailsPlan comparison, payments, and quotas. Developer workflowRepository structure and commands. TroubleshootingCommon issues and what to check first. Release notesRead major product changes.

Who this guide is for

Guest usersTry the IDE immediately with a starter quota before creating an account.

Registered usersManage projects, configure AI providers, and monitor plan usage from preferences.

Teams and administratorsReview subscription plans, billing methods, and user-management behavior.

Developers and contributorsWork inside the monorepo, services, and runbooks to extend the platform.

Getting started

1. Choose how to enter the IDE

Guest mode: Best for evaluation and quick demos. You can open the IDE without full registration.
Registered account: Recommended for ongoing work, saved preferences, subscription upgrades, and billing history.
OAuth or email login: Deployments can support email/password plus providers such as Google, Microsoft, and Apple.

2. Open your project workspace

Launch OnlineAIIDE in the browser.
Open a folder or project from the file explorer flow.
Wait for the workspace tree to populate in the left sidebar.
Open files in tabs and use split views if you need side-by-side editing.

3. Configure essentials before coding

Open your preferences panel and set theme, language, and timezone.
Configure the AI provider you want to use for chat and completion.
Review your current plan in the subscriptions section to understand available quota.
Confirm that your terminal, build, and debug features are available for the current project type.

Tip: If you hit a feature limit as a guest or free user, open the subscriptions area from preferences. The IDE is designed to guide you to the plan and billing flow when additional capacity is needed.

Feature handbook: how to use OnlineAIIDE

Code editorUse Monaco-powered editing with syntax highlighting, multi-tab editing, search/replace, folding, and IntelliSense-style assistance.

Explorer-aware file managementCreate, rename, move, and delete files or folders from File Explorer, Project Explorer, or Package Explorer depending on workspace type.

Integrated terminalRun shell commands from the bottom panel to inspect files, execute scripts, and validate builds without leaving the IDE.

Run, build, test, and debugUse the Run menu plus project-level actions for execution, build pipelines, unit tests, and breakpoint-driven debugging.

AI assistanceAsk questions, generate code, explain failures, and update files directly from the AI panel.

Source control and deploymentReview branch state, push, pull, fetch, sync, and use Deploy To flows for supported project types and server configurations.

Editor and navigation

Open files from the sidebar using File Explorer, Project Explorer, or Package Explorer.
Use multiple tabs for related files.
Use split layouts for reviewing implementation and test files together.
Java workspaces can default to both Project Explorer and Package Explorer for faster navigation.
Use fast file search and command search to jump around larger workspaces.
Use semantic navigation features such as go to definition and find references where supported.

Terminal, execution, builds, and tests

Open the terminal from the Run menu or lower panel controls.
Run project commands such as npm, pnpm, mvn, or javac according to your stack.
Use build actions for repeatable project compilation flows.
Use project actions such as Run Unit Tests… and Debug Unit Tests… where supported.
Workspace and project runtime preferences are used for language-aware execution and diagnostics.
Watch for quota messages if your plan limits executions or builds.

Debugging workflow

Set breakpoints in the editor margin.
Start debugging from the Run menu.
Use debug controls to continue, pause, inspect, and stop execution.
Loop-scoped and conditional variables are surfaced more reliably in current Java debugging workflows.
Debug quota is tracked separately from program execution quota on limited plans.

Source control, deploy, and preferences

Use source control actions to review branch context and perform push, pull, fetch, and sync operations.
Use Deploy To for supported project types such as web applications, services, and runtime-backed stacks.
Manage server configurations, themes, runtime preferences, personal profile details, and AI settings from preferences and dialogs.
Keep your preferred provider and model saved so each session starts faster.

Keyboard-friendly usage: power users should rely on quick-open, command search, and project-level context actions for faster navigation in larger workspaces.

AI assistant guide

What the AI can help with

Explain code, APIs, stack traces, and compiler errors.
Generate new files, classes, helpers, and test scaffolding.
Review code and suggest refactors or bug fixes.
Update files directly from the AI panel when the response includes supported file-operation instructions.
Support multi-provider setups including Ollama, OpenAI, GitHub Copilot, and Anthropic Claude, depending on deployment configuration.

Recommended AI workflow

Open the AI panel.
Choose a provider and model in preferences if needed.
Ask a concrete task, for example: “Create a React form”, “Explain this error”, or “Refactor this module”.
Review the generated answer before applying changes.
Track AI request usage in the subscriptions section if you are on a limited plan.

Important: AI requests count against the AI assistance quota on guest, free, and some paid plans. If you see provider or quota errors, check your configured API key, provider availability, and current plan usage.

Accounts, preferences, and user management

Authentication optionsOnlineAIIDE supports registered users and guest users, with email/password, OTP-assisted flows, and optional OAuth providers in supported deployments.

Profile settingsUpdate display name, theme, language, timezone, communication preferences, runtime choices, and AI provider settings from preferences.

Session trackingThe platform records activity such as file edits, executions, debugging, AI requests, billing events, and login activity for analytics and enforcement.

Admin capabilitiesAdministrative users can manage subscription plans, payment configuration, legal documents, and operational settings through admin-facing screens and services.

Subscription details, billing, and quotas

OnlineAIIDE tracks quota across five resource categories: program executions, debugging sessions, project builds, project size, and AI assistance requests. Guests and registered users see different plans. Premium plans increase or remove usage ceilings and add support benefits.

Guest

Guest Plan

Free / evaluation

20 program executions
20 debugging sessions
20 project builds
10 MB project size
10 AI assistance requests

Registered

Free Plan

Free / month

100 program executions
50 debugging sessions
50 project builds
20 MB project size
30 AI assistance requests

Pro

$49 / month

Unlimited program executions
Unlimited debugging sessions
Unlimited project builds
100 MB project size
150 AI assistance requests
Priority support

Premium

Pro+

$99 / month

Unlimited program executions
Unlimited debugging sessions
Unlimited project builds
500 MB project size
300 AI assistance requests
24/7 premium support

Pricing is shown from the latest available plan configuration.

Plan	Who it is for	Best use case	What to monitor
Guest	First-time visitors and product evaluation	Trying the IDE before registration	Execution, build, debug, and AI request quotas can be reached quickly
Free	Registered users with light usage	Personal experiments, tutorials, and short sessions	All tracked quota categories, especially AI requests and project size
Pro	Professional users	Regular coding, debugging, and build-heavy workflows	Project size and AI request volume
Pro+	Advanced users and teams with larger workloads	Higher-capacity workspaces and premium support expectations	Mainly project size and AI usage planning

How billing works

Available plans are shown in the subscriptions area of preferences.
Users can review the current plan, usage progress bars, and remaining quota.
Paid upgrade flows collect billing details before checkout.
Deployment configuration can support payment methods such as card payments via Stripe, PayPal, bank transfer, and UPI. Some deployments may also enable regional gateways such as Razorpay.

Pricing notes

Default public plan pricing is monthly in the current configuration.
Some environments can offer additional billing-cycle options.
Location-aware pricing may be shown automatically. For example, Indian users can see INR pricing based on browser locale or timezone signals.
Admins may maintain available plans and active payment configurations from admin-facing tools.

Usage enforcement: guest usage is intended as a starter experience and may be tracked with IP-based enforcement in addition to session-level controls. Registered users should monitor their current plan in preferences for the most accurate remaining quota.

Developer guide

The repository is organized as a monorepo with frontend apps, backend services, shared packages, infrastructure, scripts, and runbooks. If you are extending the IDE, start with the areas below.

apps/webReact and Vite frontend for the browser IDE, editor UI, panels, preferences, menus, and public documentation pages.

apps/gatewayAPI gateway handling web requests and orchestrating backend interactions.

services/authAuthentication, subscriptions, payment transactions, billing data, and user management.

services/code-intel / java-language-provider / debug-bridgeLanguage intelligence, Java tooling, and debugging infrastructure.

packages/ui / logger / tsconfig / eslint-configShared UI elements, logging utilities, and common project configuration.

runbooks / infra / scriptsOperational documentation, deployment assets, and automation helpers for local and production workflows.

Local development basics

Install Node.js 18+ and pnpm 9+.
Run pnpm install from the repository root.
Use pnpm dev to start workspace development tasks.
Use pnpm build, pnpm lint, and pnpm test for validation.

Where to read next

README: architecture, technology stack, and setup.
runbooks/AI_FEATURES_AND_CHAT.md: AI workflows and file operations.
runbooks/PAYMENT_AND_SUBSCRIPTION.md: billing and API details.
runbooks/USER_MANAGEMENT_AND_AUTH.md: authentication and user lifecycle behavior.
runbooks/DEPLOYMENT_AND_INFRASTRUCTURE.md: deployment, persistence, and operations.

Troubleshooting and support

AI requests failCheck provider keys, model selection, quota status, and network access to the configured provider.

Build or execution is blockedReview your current plan usage. Executions, builds, and debugging each have separate counters on limited plans.

Billing or upgrade issuesRe-open the subscriptions panel, verify billing details, and confirm the payment method enabled by your deployment.

Workspace confusionRe-open the project folder and verify the active explorer mode, workspace path, and runtime preference before running commands.

Source control actions failCheck your remotes, authentication, and current branch state before retrying push, fetch, pull, or sync.

Deploy action unavailableDeploy To is intentionally project-aware. Confirm the current project type supports deployment in the active workspace.

Need deeper product details? Review the release notes, privacy statement, and runbooks directory for implementation-specific behavior, environment setup, payment configuration, and deployment instructions.