A local web tool that remote-controls your PC screen, files, and AI coding agents from any browser.
View a local or remote Control server screen, and control it with keyboard and mouse when needed.
Browse allowed server folders to view, edit, share, and upload files, with Git and SVN support.
Search files by name across registered paths.
Open AI chat sessions with a working directory, run several at once, and follow status by color.
Open CLI sessions such as cmd, claude, codex, opencode, antigravity, and grok, and hand work off to another provider with a slash command.
Runs Sub Agent tasks automatically on a schedule.
Open a remote web view by URL and size, and send keyboard and mouse input when needed.
Register reusable AI agents with provider, model, and options for Team and Schedule.
Set a goal and run selected sub agents in parallel under a supervisor agent.
Edit code and text in place, and open spreadsheets or local SQLite tables in dedicated viewers.
Split the center panel into panes to use Chat, Terminal, Browser, and RDP side by side.
Point to an Ollama or LM Studio server and use its models like any other provider.
Review past AI sessions from Chat, Terminal, and more, and delete them when you no longer need them.
Connect Telegram, Discord, or Email for chat, Terminal link, and two-factor approval.
Real situations, plain language — one need or several at once
node *ai/tool/tsc_check to pass without a prompt/codex — hand off and continue without re-explaining/claude for design, then /grok for the restScreen layout matches the actual application
Local:./, remotes as host:path). F2 = all checked; path ⋯ → Search = that path only (toggle others anytime). Search all checked scopes (partial name, Stop, max 200). Results show server:folder; file → Editor; folder → right File list when that scope is the current File root.?path=, File opens instead.tutorial.html file...Path checkboxes list every registered root (local + authenticated remotes). F2 checks all; path-group ⋯ → Search checks only that path. Search runs on every checked scope (partial name, Stop, max 200). Excludes node_modules and hidden folders.
Registers a local Ollama or LM Studio server as an OpenCode model provider. Paste the address in any form (127.0.0.1:11434, a full URL, even a /v1/models link) — only the IP/port are extracted. The model list is fetched automatically and written into opencode.json.
| Connection | Provider | Host | Models |
|---|---|---|---|
| Connected | Ollama | 127.0.0.1:11434 | 3 |
| Disconnected | LM Studio | 127.0.0.1:1234 | 0 |
Server working folders, served as /Root0, /Root1… (one per line). Saving writes to Env.json and restarts the server to re-register the routes.
Time mode: pick days of week (Sun–Sat), hour (0–23), minute (0/5/…/55), and optional Run once then delete.
Delete all conversation history older than 1 month(s)? This applies to every project on this machine and cannot be undone.
SQLite opens db/artgine.sqlite directly (read-only). DB Viewer first asks for connection info (type/host/database) for MySQL, MSSQL, or another SQLite file.
| id | name | created |
|---|---|---|
| 1 | artgine | 2026-01-04 |
| 2 | session_log | 2026-03-11 |
Two ways to get started right away
start.bat./start.shnpm run start_web [port] (omit the port to use the one from settings.json)npm run start_localArtgine.exe./Artgine --no-sandboxArtgine.appDownloaded executables are often blocked by the OS. Fix it per platform, then run Artgine again.
.zip or Artgine.exe → Properties → check Unblock → Apply. Or in PowerShell: Unblock-File -Path .\Artgine.exechmod +x ./Artgine (or the actual executable name inside the zip), then ./Artgine../Artgine --no-sandbox.noexec mount; move it to your home folder if needed.xattr -dr com.apple.quarantine /path/to/Artgine.app (or the unzipped folder), then open again.chmod +x ./Artgine then ./Artgine.[port] with the port shown in the Electron Server panel or in settings.json.localhost.
Full engine guide (modes, install, workflow, EN/KO): https://06fs4dix.github.io/Artgine/help/help.html
Change the Control login password before publishing the URL outside your local network. Anyone who knows the default can open files, terminals, and RDP.
password field in settings.json, usually located in the working directory the server was started from. A short plain-text value there is hashed automatically on the next login check.Artgine Control can reach the screen, files, terminals, and AI agents on the host PC. Strengthening the OS account and folder rights is far more effective than relying on the web password alone.
artgine) and run the server under that account — not your daily admin / root login.sudo -u ….C:\ or /) in the working-folder list unless you truly need it.Also change the default web password, keep the server off public networks when possible, and use VPN/reverse-proxy auth if you must open it remotely.
Each project can keep an ai/ folder at its root — the AI coding agent (Claude, Codex, ...) reads it before working on that project, so project-specific rules and permissions live there instead of in the assistant's memory.
artgine/) APIs before writing new logic.CLAUDE.md tells the agent which guide here to read before that kind of task.ai/settings.json is separate from the server's root settings.json (login password, working folders). Besides the models list shown in Chat/Terminal dropdowns, its permissions.allow / permissions.deny arrays control auto-approval of the permission prompts that Claude/Codex/Grok/opencode print inside a Terminal PTY session (e.g. "Allow this command? y/n"). Chat UI sessions do not use this prompt auto-approve path.
Each rule can test type ("read" | "write" | "reply" — read vs. file-changing action), tool (the CLI's tool name, e.g. Bash, Edit, MCPTool), and/or command (a prefix of the actual shell command, * wildcard supported). On a prompt, deny rules are checked first, then allow; if neither matches, SUPER mode in that Terminal session (F6 / /super / ⌨ → ⚡ SUPER) auto-approves everything else, otherwise it just waits for you to click.
Examples
{ "type": "read" }tsc_check_bad:{ "command": "node *ai/tool/tsc_check" }{ "type": "write", "tool": "Bash", "command": "npm test" }deny wins over both allow and SUPER:{ "command": "rm -rf" } (in permissions.deny){ "tool": "MCPTool" } (in permissions.deny)Node.js is required; CLI providers install themselves when you open a Terminal
Artgine and the AI CLIs need Node.js on the machine that runs the server. Install a current LTS from nodejs.org first, then start Artgine. Check the right sidebar Info → Provider Status — Node.js should show as installed with a version.
You do not need to install each provider CLI by hand. When you open a new Terminal (or Chat) for claude, codex, opencode, agy, grok, and so on, the missing tool is installed automatically on first use. Wait for that step to finish if the session shows busy / installing.
Installation is automatic — login and subscription are not. Link your personal account for each provider in advance (API key or browser login). Use the provider’s normal linking flow on its web site or inside a Terminal session — same as using the CLI alone. Until authenticated, Provider Status may show Not Authenticated and the agent cannot run real tasks. After auth, refresh Info if needed.
Tip: open Terminal once per provider so auto-install can finish, complete personal-account linking on the web or in Terminal when prompted, then confirm status under the right sidebar Info tab.
Operate every feature without a mouse
A detailed breakdown of every part of the screen
Four areas. Click a card or a TOC entry to jump.
Opens File, Multiplexer, and the More menu for new sessions and tools
Picks RDP targets and lists open Agent / Other sessions
Shows the screen for the tab or session you selected
Info, path files, and Option settings for the current work
Above the center panel: File, Multiplexer, and a More dropdown (Memo, RDP, Chat, Terminal, Browser, Team, Download, Log, Messenger, Help). File search is not a top tab — F2 or path ⋯ → Search open a multi-path checkbox modal. Several items open a dialog first — expand below to see the real content.
Center panel (top tab) — opens the full file manager for the current root. Details: Center → File.
Center panel (top tab, not under More) — multi-pane layout in the center. Full modes / split / merge / content select: Center → Multiplexer.
Dropdown for everything that is not File / Multiplexer. Two open styles: (1) Modal then center — RDP / Chat / Terminal / Browser / Team: create dialog is documented here under More; after Open, check Center Panel for the live UI (each item links there). (2) Center only — Memo / Download / Log / Messenger / Help: no dialog; full how-to is under Center only (More is a short link). File search is F2 / path ⋯ → Search, not in this menu.
There is no top Search tab. Both entries open the same Control-page modal (not the File iframe):
Checkboxes are serverLabel:rootPath. Type a partial file name → Search / Stop; scans each checked root from / (skips node_modules / hidden), max 200 hits total. Results show server:folder; click a file → Editor; click a folder → right File list only when that scope is the current File root.
Center panel (no dialog) — opens the Memo page in the center. Full layout, modes, and slash commands: Center → Memo.
Opens a one-field modal — paste a remote Control.html URL and Add — to register it in the left sidebar's RDP list. After it is listed, select it on the left to open the live screen in the center — details: Center → RDP.
Opens a modal for a new AI chat session — Working Directory plus the same MCP / Copy MD switches as New Terminal, then Open. The session appears under left Agent in that path group. This block is only the create dialog; the live chat UI is under Center → Chat.
CLAUDE.md / AGENTS.md / …).Always opens the New Terminal modal first (also F3). Pick mode, optional Key, Working Directory, then MCP / Copy MD, and Open. Existing sessions open from left Agent path groups — not this button. This block is only the create dialog; input bar, SUPER, handoff, Log: Center → Terminal.
cmd (plain shell), or AI CLIs claude / codex / agy (antigravity) / opencode / grok. Missing CLIs install on first open.CLAUDE.md, AGENTS.md, …) so project rules and paths apply. No-op for cmd or when cwd is already the server root.Opens a modal for a new web session — URL, Browser (auto/chrome/msedge/firefox), TTL, screen size, and Stealth time. This is only the create dialog; live page / Frame / Input after open: Center → Browser.
Opens a modal to pick the main agent's Provider/Model, a Goal, sub agents to dispatch to, and a time limit — the running team shows up as a Terminal session under left Agent. Create options are here; the live PTY UI: Center → Terminal.
Center panel (no dialog) — opens the yt-dlp/ffmpeg download helper in the center. Full UI (URL, MP3/MP4/Direct, jobs): Center → Download.
Center panel (no dialog) — opens provider conversation logs in the center. Full accordion / refresh / delete: Center → Log.
Center panel (no dialog) — opens the Messenger panel in the center (top text box + Register + Email button, session list). Full Telegram / Discord / Email setup (where to paste the token, SMTP/IMAP then peer): Center → Messenger.
Center panel (no dialog) — opens this guide (Promo / Getting Started / Guide / FAQ) in the center; also the default first-open panel. ?path= entry opens File instead.
Top to bottom: RDP list, then Agent / Other sub-tabs. Agent groups Chat/Terminal by working directory; Other lists Browser/Editor newest-first.
At the top of the left sidebar. Local is always present (this server's screen); below it, any Remote Control.html servers you've registered (via More → RDP). Click one to view its screen in the center; turn on Input to forward keyboard/mouse.
Agent holds Chat and Terminal, grouped by working directory. Other holds Browser and Editor in a flat newest-first list. The active sub-tab is remembered; opening a session auto-switches to the matching tab.
Visible on the Agent tab. Edits the server's allowed root folders (one path per line). Registered paths show as empty path groups even with no sessions. Saving restarts the server.
Each group is one working directory (long paths show the tail). Click the header to collapse/expand. Empty registered folders still appear so you can start work there.
⋯ menu on the path group — three things you can do here:
Sessions created from Chat/Terminal land under this same path group in the Agent list.
Chat / Terminal / Browser / Editor show a colored status dot. RDP items do not — Local is just a label, Remote shows its URL.
Chat and Terminal items live under their path group. Click to open in the center. Create new ones from More → Chat / Terminal (F3), or from a path group's ⋯ menu (Chat / Terminal / Search).
Browser and Editor are listed flat under Other (newest first). New Browser: More → Browser. Editors appear when you open a file from the File tab or the right-sidebar File list.
The center panel shows whichever tab or session is active. Each type below is explained one at a time, with the real sample screen next to it.
Shows the target screen (Local or a registered Remote server) as a live series of screenshots. Frame controls how often it refreshes and Quality controls image compression. Turning on Input forwards your keyboard and mouse to that screen.
Full file manager for the current root (File.html in the center). Top bar: root selector, path URL, copy. Toolbar: Music, sound-add mode, Search, File (admin modal). Folder list with type icons; Git/SVN badges (M/A/D/?) when available.
Open by type
file-opened so Control opens an Editor session under the left Other list (Monaco / sheet / MD path). HTML may ask Edit vs Execute (new window).Search
node_modules; can Stop mid-scan; results capped (about 200).File modal (admin)
A live PTY session (xterm) in one of six modes — cmd, claude, codex, agy, opencode, grok. AI modes show a running transcript with a bottom input bar; plain cmd is a normal shell. Open new ones from More → Terminal (F3) or a path-group ⋯; switch existing ones from the left Agent list.
Layout & input
SUPER (auto-approve)
/super, or ⌨ menu → ⚡ SUPER. While on, the input field uses a red border/background — that is the only on-bar visual (not a SUPER button).Slash commands & provider handoff
/ to open autocomplete: built-ins like /compact, /resume, /model, /clear, /status, /exit, /help, /super, plus registered Skills and handoff targets./codex, /claude, /agy, /opencode, or /grok (other than the current mode). The session summarizes (up to ~3 min), then Control opens a new Terminal on that provider in the same working directory. Input is locked during the handoff. Not used in pure cmd mode./ is remapped to Latin keys so slash commands still match on a Korean keyboard.⌨ menu (mobile / precision)
/model prefill), COMPACT, CLEAR, STATUS, EXIT — mapped per provider (e.g. Gemini uses /stats for status).Files into the prompt
.uploads/ and inserts the server path in quotes into the input.Start options (MCP / Copy MD)
A structured AI chat thread rather than a raw terminal — user/assistant message bubbles with a composer at the bottom. Multiple chat sessions can run side by side, each tracked under left Agent in its working-directory group.
*.md into a non-root working folder).Remotely drives a Playwright browser session — shows the live page and its address bar. Frame/Quality control the screenshot refresh rate and compression the same way RDP does; turning on Input forwards your keyboard and mouse to the page.
Opens a file selected from the File tab in a Monaco-based code editor. Excel/CSV files open in a spreadsheet-style grid instead, and local DB files (SQLite etc.) open in a table viewer — both editable in place, not just previews.
Embeds Artgine’s Memo page — a folder-scoped note log with a category sidebar, mode/provider top bar, chat-style log, and bottom composer. Open from More → Memo.
Layout
#tag in the text.Modes & slash commands
A leading slash on a send overrides the dropdown for that one message only. Hangul jamo on the same keys still match (e.g. ㅈ for /w position).
/w <text> — Write: save a memo (no category selected → auto-classify from content)./s <query> or /r <query> — Search: AI search in the selected category, or all if none selected./d … — Delete:
/d 12)/m <id> or /m @id — Move: move that memo into the currently selected category (select destination first).Without a prefix, the top mode dropdown applies. Without a category in Write mode, pick one or let auto-classify run.
A download helper backed by yt-dlp/ffmpeg (status badges show whether they're installed). Paste a YouTube or direct file URL, fetch its info, pick MP3/MP4/Direct, and Start — each job shows a live progress bar and its final file name.
An accordion of past AI conversations across every provider — Chat and Terminal sessions both log here. Each entry shows a model badge, a one-line preview, working directory, and timestamp; expand it to read the full exchange. Refresh/delete-all sit in the header, and each entry has its own delete.
Open with More → Messenger (center panel, no extra dialog). Top toolbar of this panel:
Below: accordion of registered sessions (Telegram / Discord / Email). Expand one for join/invite link, Terminal Link, direct message, log.
1) Telegram — create bot → paste token → Register
@BotFather./newbot → set display name and username (must end with bot).7123456789:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw (digits + : + secret). Copy the whole string.https://t.me/YourBotUsername → send /start (or any message). State pending → active.2) Discord — create bot app → paste token → Register → invite
MTIz.ABC.xyz (three segments separated by ., no colon).3) Email — first server mail account, then register who may reply
Email is two steps. Do not put SMTP passwords into the Register text box. Order matters.
Step A — add the server’s mail account (must be first)
smtp.gmail.com)465 or 587)you@gmail.com (not just you)imap.gmail.com)993)Step B — register the peer address (who is allowed to talk back)
friend@example.com.After registration (any platform)
Open from the top Multiplexer tab. Split the center into panes and show several live sessions at once (Chat, Terminal, Browser, RDP). Layout persists in localStorage.
Modes
Menu (top-right ⋯)
Content select
The right sidebar has three sub-tabs — Info, File, and Option — explained one at a time below. Option itself bundles eight separate controls, each broken out individually.
Provider Status shows Node.js and each AI provider with install/auth state, version, and remaining usage (5h / Weekly). Below that, completed Chat/Terminal notifications are listed.
A lightweight file browser separate from the full File tab — navigate folders and open a file straight into the Editor tab.
Bundles eight controls in one panel: Theme, local model registration, Two-Factor Auth, Database viewers, history cleanup, Schedule, Sub Agent, and the shortcut list. Each is broken down individually below.
Switches the whole app between Light and Dark.
Registers a local Ollama/LM Studio server and checks its connection status. Each button opens its own modal:
platform - botName).SQLite viewer and a generic DB (MySQL/MSSQL/SQLite) viewer for browsing local data files.
Bulk-deletes old AI conversation logs older than the given number of months.
Keyboard shortcut summary at the bottom of the Option panel (F1–F7, arrows). Full list with descriptions is also under Getting Started → Keyboard Shortcuts. Present in Control UI: right sidebar Option → Help.
Short answers — use the links for full screen detail (no long duplicates here)
1) Register an active Messenger session. 2) Right sidebar Option → Two-Factor Auth → pick that session (saves immediately). Login then waits for messenger approval (~5 min). Disabled turns it off.
Default is artgine. Change it in the Electron Server panel, or set password in settings.json (plain text is hashed on next check).
More → Messenger top text box = bot token or peer email → Register. Telegram/Discord: create bot outside, paste token there. Email: click Email first (SMTP+IMAP Verify&Save), then paste peer address → Register. Optional: Terminal Link / 2FA.
Open More → Terminal / F3, pick mode (cmd / claude / codex / …). AI providers need your personal account linked in advance (login / subscription). Complete that with the same normal linking flow you would use on the provider’s web UI or inside a Terminal session — Artgine does not replace that step. Handoff with /codex etc.; SUPER via F6 or /super. Install/auth status: right Info tab.
These two npm scripts start Artgine differently — pick one:
npm run start_local → runs node desktop/Start.js local_settings.json. Opens the Electron UI (desktop shell / Server panel) using local_settings.json.npm run start_web → runs node desktop/WebStart.js. Starts the web server only — no Electron window. Open Control in a normal browser at http://localhost:[port]/Artgine/…. Optional: npm run start_web -- [port] (omit port to use settings.json / default).npm start is the usual Electron start with default settings.json. Do not expect start_web and start_local to look the same — one is headless server, the other is the local Electron app.