Product documentation

ScriptExpert documentation

Installation, first project, AI Agent configuration, local development services, database tools, publishing, updates and troubleshooting for version 0.1.96.

Getting started

System requirements

Windows

Windows 10 or Windows 11, a modern 64-bit processor, at least 8 GB RAM and sufficient storage for the application, projects and local databases.

Linux

A supported 64-bit desktop distribution with the standard libraries required by Electron applications. Package requirements may vary by distribution.

AI provider requirements

Cloud providers require credentials issued by that provider. Ollama and LM Studio can run local or remote models without sending project prompts to a commercial cloud API.

Installation

Install on Windows

  1. 1
    Use the Windows download button to obtain the installer configured by the website owner.
  2. 2
    Run the installer and choose the installation location. Allow the installer to finish copying the desktop application and any packaged runtime components.
  3. 3
    Launch ScriptExpert. Open Settings to choose a theme, language, terminal shell and AI provider.
  4. 4
    Create or import your first project, then verify the Local Server page if you plan to run PHP applications locally.
Installation

Install on Linux

  1. 1
    Use the Linux download button to retrieve the current package.
  2. 2
    Install the package using your distribution's package manager or make the provided application executable when using a portable build.
  3. 3
    Start ScriptExpert from your applications menu or terminal and confirm that the selected terminal shell is available.
  4. 4
    When using local development services, verify that required ports are available and that no other Apache/MariaDB service conflicts with them.
Projects

Create or add a project

Open Add Project, choose a project name and local folder, then save the project. ScriptExpert uses the selected folder as the protected workspace boundary for file and AI operations.

  • The project list shows project names, folders, last updates and actions.
  • Removing a project from ScriptExpert does not automatically delete its files from disk.
  • Project settings can store a custom prompt, detailed instructions, AI skill selection, MCP server selection, database settings and FTP publishing details.
Workspace

Editor and file manager

The central editor is based on Ace and is surrounded by the active project's file tree and optional AI panel. Open multiple files in tabs, edit code, save changes, preview the current project and publish through FTP when configured.

Editor workspace
ScriptExpert editor workspace

The dedicated File Manager provides a broader view for browsing project folders and managing items. AI file tools are restricted to the open project root.

Artificial intelligence

Configure and use the Cline Agent

Open Settings → AI, keep Cline as the selected agent, choose a provider, enter the provider URL or API key when required, and select separate Plan and Act models where available.

The Agent can analyze the active file and broader project, read images, search text, read file contents, write complete files, create folders, create ZIP archives, download resources, delete approved paths, run terminal commands and use database tools. The exact available actions depend on the current mode and access level.

Review destructive operations

Full access permits direct file, terminal and database changes. Use it only for trusted tasks, maintain backups and review diffs or approval prompts before applying important changes.

AI configuration

Supported providers

ScriptExpert includes thirteen provider profiles:

OpenAIOpenAI-compatible customOpenRouterGroqGoogle GeminiGitHub ModelsCerebrasTogether AIDeepSeekMistralxAILM Studio localOllama local

Cloud and hosted providers: OpenAI, OpenRouter, Groq, Google Gemini, GitHub Models, Cerebras, Together AI, DeepSeek, Mistral and xAI generally require a provider account and API key. Free quotas or free models depend on each provider and may change.

Custom and local providers: OpenAI-compatible custom accepts a compatible endpoint. LM Studio local commonly uses http://localhost:1234/v1. Ollama local commonly uses http://localhost:11434 and can also point to another machine on your network.

Agent safety

Plan, Act, Limited and Full access

SettingPurposeTypical behavior
Plan modeAnalysis and planningReads context and proposes steps without writing files or running terminal changes.
Act modeExecutionAllows approved tools to change the project, depending on access level.
Limited accessReview-first workflowRequires approvals and restricts direct changes.
Full accessAutonomous project workPermits direct file, directory, terminal and database operations inside the active project.
Advanced AI

Context, project instructions, skills and MCP servers

Use global AI settings to control context length, thinking depth, maximum iterations, timeout and automatic context compression. Project settings can add instructions specific to a framework, repository or workflow.

  • Custom skills: import reusable instructions and workflows.
  • Custom tools: expose additional approved capabilities to the Agent.
  • MCP servers: configure and select Model Context Protocol servers per workspace; connected tools may request approval before execution.
  • Shortcuts: use the AI toolbar to change model, context and tool configuration without leaving the conversation.
Development workflow

Integrated terminal and browser

The terminal starts with the current project as its working directory. On Windows, select the desired supported shell in Settings. The AI Agent follows the configured project terminal when composing commands.

Use Preview from the editor to start or open the local project URL. The embedded browser supports navigation and reload while keeping the editor and AI conversation visible behind or beside the preview.

Development stack

Local Server

The Local Server page manages the bundled Apache, PHP and MariaDB components. Each service card shows runtime information, status, port, path and controls for starting, restarting, stopping or configuring the component.

Local Server
Local Server page
Data tools

Database Manager and Database Browser

Open the database manager from Local Server or the editor database tab. Connect using project settings or the local MariaDB service, then select a database and table.

  • Create databases and tables.
  • Add or modify table columns.
  • Browse and edit table rows.
  • Import SQL files and export databases or individual tables.
  • Use Agent database tools for connection tests, schema discovery, row reading and approved SQL execution.
Reusable code

Snippets

Create categories and reusable code snippets from the Snippets panel. Snippets remain available across editing sessions and can be organized by framework, language, component or task.

Publishing

Save and publish to FTP

Add FTP connection details in the project's custom settings. In the editor, use Publish FTP to upload the current file, or choose the project publishing action to upload a larger project selection.

Credential safety

Use a restricted FTP/SFTP account when possible. Do not share saved credentials in screenshots, support messages or source repositories.

Extensions

Plugins

The Plugins page lists installed extensions, their versions, status and available actions. The Free edition can use free plugins; Pro can use free and paid plugins subject to the license terms of each extension.

Personalization

Application settings

Settings include update checks, Day/Night appearance, autosave interval, default terminal, application language, AI provider, separate Plan/Act models, context settings, iteration limits, task timeout, skills, tools and MCP configuration.

The interface is available in English, Deutsch, Español, Français, Italiano, Magyar, Português, Română, Türkçe, Ελληνικά, Русский, العربية, हिन्दी.

Maintenance

Automatic updates

Use Settings → Updates → Check now. The updater contacts the configured update service and reports whether a newer compatible release is available. Back up important projects before major upgrades even though project data is stored separately from the application package.

Help

Troubleshooting checklist

Verify the endpoint, API key, selected model and network access. For Ollama, confirm the service is running and at least one model is installed. For a remote Ollama host, verify the IP address, port and firewall.

Select an active project, start the required local server services, check the project URL and confirm the configured port is not used by another application.

Start MariaDB, verify host, port, user, password and database settings, then use the connection test before browsing tables.

Confirm the command matches the configured shell and that required executables are available in PATH. The Agent writes commands for the shell selected in Settings.

Switch to Act mode and review the current access level. Full file changes require the appropriate access and may still require approval.

Use the Support link in the header for tickets or the Contact page for sales, licensing and general questions.