How to Open Copilot — Web · Home Screen App · Windows App
The Copilot screen is served by the Copilot server at your installation site. There are three ways to open it, and whichever you use, you get the same screen, same account, and same permissions.
| Way to open | When to use | What to install |
|---|---|---|
| Web browser | Just opening it on an office PC or laptop | None |
| Home screen app (PWA) | Opening it like an app on a field phone/tablet, and receiving push notifications | «Add to Home Screen» from the browser |
| Windows desktop app (in preparation) | Keeping it as a single window in the taskbar instead of a browser tab | A single installer file |
Get the address from your administrator — e.g. https://copilot.<회사>.local. It must be an HTTPS address for the microphone (voice questions) and push notifications to work.
Web browser
Open the address in a recent version of Chrome, Edge, Safari, or Firefox. After logging in, the first screen is Ask → Copilot Screen Map.
- The first time you open it, the screen language follows your browser's language setting (Korean or English). You can change it below the login screen with 한국어 · English.
- If you open a link from an email or notification while not logged in, the login screen appears first, and after logging in you're taken to the screen that link pointed to.
- If the server is upgraded to a new version while you've left a tab open for a long time, a "New version available" notice appears at the bottom of the screen — same as under «Home Screen App» below.
Home screen app (PWA)
Add Copilot, opened in a browser, to your phone or tablet's home screen as if it were an app. It opens without an address bar and can receive push notifications.
| Device | How to add |
|---|---|
| Android (Chrome) | Open the address and from the ⋮ menu choose Add to Home Screen (or Install App) |
| iPhone/iPad (Safari) | Open the address and choose Share → Add to Home Screen |
| PC (Chrome/Edge) | Click the Install icon on the right side of the address bar |
There is no separate install button inside the Copilot screen itself — it's added via the browser's menu as described above.
- The app's name and icon follow the installation's brand settings (product name, favicon, or logo). When you open the added app, it starts at the Ask screen.
- After adding it, turn on "Phone/browser notifications" under Settings › Notifications. On iPhone/iPad, push notifications only work from the app added to the home screen.
- It can only be added from an HTTPS address, and the device must trust the server's certificate — if the certificate was issued by an internal certificate authority (CA), register that CA on the device first. If opened with an untrusted certificate, the screen will still display, but push notifications and the «When disconnected» behavior described below won't work.
New version notice — When the server is upgraded to a new version, a "New version available" message and a Refresh button appear at the bottom of the screen. Pressing it switches to the new screen — there's no need to reinstall.
- It does not refresh itself automatically, in order to protect what you're writing. The notice also won't disappear until you press it — press it after you've finished your input.
- Whether a new version is available is checked when you return to the app (tab), and every 30 minutes while it stays open.
When disconnected — If the network drops while you're using the app, a banner appears at the top of the screen reading "Internet connection lost. You can resend once reconnected." If you open the app while disconnected, instead of content you'll see "Internet connection lost. …" or "Could not connect to the server. Check your network and try again," or "Unable to connect" with a Retry button. Plant data, answers, and lists are not stored on the device, so content only appears once you're connected.
Windows desktop app
The Windows desktop app is not yet publicly available. The guide below describes the version that will be released, and the download address will go live at the time of release. Until then, please use the web browser or home screen app.
This is a thin window that opens the address of the Copilot server at your installation site. The screen content isn't bundled inside the app — it displays whatever screen the server serves — so when the server is upgraded to a new version, the app doesn't need to be reinstalled. The only screens the app itself owns are Server Address and Unable to Connect.
| Item | Value |
|---|---|
| Support | Windows 10/11, x64 |
| Install | Per-user install — no administrator rights required. You can choose the install location |
| Size | About 106 MB |
| Auto-update | None (to account for air-gapped network installs). For a new version, rerun the installer to overwrite |
| Code signing | None — a Windows warning appears during installation (see step 2 below) |
Download
| Version | Address |
|---|---|
| Latest | https://product.kopens.io/plantpulse-ai/desktop/latest/PlantPulse-Copilot-Setup-x64.exe |
| By version | https://product.kopens.io/plantpulse-ai/desktop/<YYYY.MM>/PlantPulse-Copilot-Setup-<version>-x64.exe |
For both addresses, there's a .sha256 file with the same name next to the installer (the versioned folder also has that signature's .sha256.sig). Verify the downloaded file with PowerShell as shown.
Get-FileHash .\PlantPulse-Copilot-Setup-2026.10.0-x64.exe -Algorithm SHA256
# 출력의 Hash 값이 .sha256 파일의 값과 같아야 합니다
If your site has no internet access, download it on an internet-connected PC and transfer it internally. Once installed, the app itself connects only to the Copilot server.
If the "latest" address seems to be serving an old file, append any number to the address, like ?v=1, and download again.
Code signing — deploying internally without warnings
The current installer has no code signing. The signing approach has not yet been decided — until then, either dismiss the warning as described in «Installation» step 2 below, or have IT add the file hash to an allowlist. Once a signed version is released, registering that signature's root certificate on the PC will let it install without the "Windows protected your PC" warning.
| Where to register | Store to add to |
|---|---|
| Group Policy (GPO) — Computer Configuration › Policies › Windows Settings › Security Settings › Public Key Policies | Trusted Root Certification Authorities + Trusted Publishers |
| Intune — Device Configuration Profile "Trusted Certificate" | Same two stores |
The certificate file address and fingerprint will be included in the release notes for the version where signing takes effect.
Installation
- Run
PlantPulse-Copilot-Setup-<version>-x64.exe. - If a "Windows protected your PC" window appears, click More info → Run anyway. This warning appears because the installer has no code signing. For a mass internal deployment, IT can add this file's hash to an allowlist via Group Policy or Intune so it installs without the warning.
- For install scope, choose Current user only (default). Shortcuts for PlantPulse Copilot are created on the desktop and in the Start menu.
To uninstall, go to Windows Settings › Apps › PlantPulse Copilot › Uninstall. User settings such as the server address remain (see «User Data» below).
Entering the server address
On first run, the Server Address screen appears. Enter the address given by your administrator and click Connect. From then on, that server's login screen opens directly.
- Only
https://addresses are accepted.http://addresses are rejected with "Only secure connection (https) addresses can be used" — if it won't open because the certificate doesn't match, don't fall back tohttp; resolve it using «Importing an internal CA certificate» below instead. If you omithttps://,https://is appended automatically. - Addresses with a path also work — e.g.
https://host/copilot. Any?…or#…after the address is discarded. - You cannot include
계정:비밀번호@in the address (it would remain as-is in the config file). Log in from the screen instead.
To change servers, use the File › Change Server… menu, or click Change Server from the "Unable to connect" screen.
Unable to connect
If the server is down or the network is disconnected, the Unable to Connect screen appears. Use Retry to reconnect, or Change Server to correct the address.
Importing an internal CA certificate
If the server uses a certificate issued by an internal certificate authority (CA), you'll initially see "Unable to connect — certificate error."
- Click Change Server → Import CA Certificate and select the CA certificate file (
.pem·.crt·.cer, PEM format). This should be the certificate of the CA that issued it, not the server certificate itself — e.g./etc/kopens/ca/root.crton the installation host. - The screen shows the CA name, expiration date, and SHA-256 fingerprint. Verify it matches the fingerprint given by your administrator.
- Once the CA is imported, the app restarts itself — a restart is needed to re-evaluate the server you just rejected under the new CA. If you had already entered the server address, it opens directly after the restart. The app also restarts when you remove an imported CA.
An imported CA is used only for the configured server. It has no effect on certificate evaluation for other sites, and does not disable certificate verification — hostname, validity period, and signature are still checked as usual. DER (binary) format files are not accepted, so convert to PEM before importing.
certutil -encode root.der root.pem
Keyboard shortcuts
| Key | Action |
|---|---|
Ctrl + + (or =) | Zoom in |
Ctrl + - | Zoom out |
Ctrl + 0 | Reset zoom |
F5 | Refresh |
F11 | Full screen |
Only one instance of the app can run at a time — running it again while it's already open brings that window to the front.
User data
The server address, window size and position (settings.json), imported CA (ca.pem), and login cookies are stored in %APPDATA%\PlantPulse Copilot\.
Deleting this folder resets the app to its first-run state.
Scope of behavior for IT administrators
| Item | Behavior |
|---|---|
| In-window navigation | Restricted to the configured server address (origin) only. Other web addresses open in the default browser, and addresses like file: are not opened at all |
| Browser permissions | Only microphone (for chat voice questions, audio only), clipboard write (for the copy button), and full screen are allowed on the server screen. Camera, location, notifications, USB, serial, etc. are denied — which is why push notifications are received via web browser/home screen app, not the Windows app |
| TLS | Certificate verification is never disabled. Internal CAs can only be added via «Importing an internal CA certificate» above |
| Execution isolation | Chromium sandbox and context isolation are enabled, and Node.js cannot be used from the screen. There is no developer tools menu |
| Network | The app never connects out on its own — there is no update check or usage telemetry, and spell-check (which would fetch dictionaries externally) is also disabled |