Source: https://www.devyy.dev/docs/installation/ Markdown: https://www.devyy.dev/docs-markdown/installation.md # Install Devyy Devyy is a desktop code editor. Local editing, search, and the terminal work without signing in. You can connect an account or AI provider later if you need it. ## Download and install Go to [Devyy downloads](https://www.devyy.dev/download/) and select your operating system. Download the package that matches your machine when the release offers multiple architectures. | Platform | Package | What to do | | --- | --- | --- | | Windows | EXE installer | Run the setup program and open Devyy from Start when installation finishes. The editor uses the Microsoft Edge WebView2 runtime. | | macOS | DMG | Open the disk image, drag Devyy to Applications, and launch it from there. | | Linux | DEB or AppImage | Install the DEB through a compatible package manager, or mark the AppImage executable and run it. | On Linux, if you're using an AppImage, replace the sample filename with the exact file you downloaded. ```sh chmod +x ./Devyy.AppImage ./Devyy.AppImage ``` ## Open a project 1. Launch Devyy. You can complete the setup flow or adjust those preferences later in Settings. 2. Press **⌘ O** on macOS or **Ctrl O** on Windows and Linux, then select your project folder. 3. Choose a file from the project explorer, or press **⌘ P** or **Ctrl P** and type part of its name. 4. Make a change and press **⌘ S** or **Ctrl S** to save it. Use the workspace name in the title bar to switch recent folders. See [Editing and navigation](editing-and-navigation.md) for search, splits, themes, and keyboard shortcuts. ## If you cannot open the app - Match the release package to your operating system and CPU. An ARM64 Mac and an Intel Mac need compatible builds. - On Windows, check that WebView2 is installed if the editor window fails to render. - On Linux, if the AppImage cannot start on your distro, try the DEB on a compatible system or check your distro’s AppImage runtime requirements. --- Source: https://www.devyy.dev/docs/account-and-sync/ Markdown: https://www.devyy.dev/docs-markdown/account-and-sync.md # Account and sync A Devyy account is optional for local editing. Use one when you want to sign in on more than one device and sync supported editor preferences. ## Connect the desktop editor 1. Open **Account & sync** from Devyy. 2. Start sign-in in the browser. Use an existing account or create one. If you register with email, verify it with the code sent to that address. 3. Confirm the device shown by the browser, then choose **Open Devyy** to return to the desktop app. 4. Review the categories in **Account & sync** and choose what you want to sync. The device authorization starts in the desktop app. If the browser says the link expired, start again from the app so it can generate a fresh request. ## Move to another device Sign in to the same account on the second device, then review its sync preferences. Sync covers selected settings and extension information. Your project files remain in the local folder or on the SSH server where you opened them. Use your usual project transfer or Git workflow to make the project available on another device. --- Source: https://www.devyy.dev/docs/editing-and-navigation/ Markdown: https://www.devyy.dev/docs-markdown/editing-and-navigation.md # Editing and navigation Open a folder before using project search or the explorer. The project tree works with files on disk. Unsaved editor changes stay in their tabs until you save them. ## Move around your project Use the file picker when you know the filename and workspace search when you know text inside a file. Workspace search respects Git ignore rules and skips generated folders. | Action | macOS | Windows and Linux | | --- | --- | --- | | Find a file | ⌘ P | Ctrl P | | Run a command | ⌘ Shift P | Ctrl Shift P | | Find or replace in the current file | ⌘ F | Ctrl F | | Search across the workspace | ⌘ Shift F | Ctrl Shift F | | Save the active file | ⌘ S | Ctrl S | | Go to a line | ⌘ L | Ctrl L | The file picker highlights matching parts of a path. Use the arrow keys to choose a result and **Enter** to open it. To review or change a binding, go to **Settings → Keyboard shortcuts** and search for the command. ## Work with two files Right-click a different file in the explorer and choose **Open in split editor**. Drag the divider to adjust the space given to each file. Selecting a tab in the pair restores its split. Opening another tab shows that file on its own. For Markdown files, use the source, preview, or side-by-side controls. You can keep editing the source while the preview updates. ## Set the Monochrome theme Open **Settings → Appearance** and choose **Monochrome**. The theme uses black and neutral window surfaces with syntax colors for reading code. Use the appearance settings to adjust window and editor transparency independently. --- Source: https://www.devyy.dev/docs/terminal-and-git/ Markdown: https://www.devyy.dev/docs-markdown/terminal-and-git.md # Terminal and Git Open the project folder in Devyy first. For Git features, have Git installed and open a folder in an existing repository. ## Open a terminal Press **⌘ + backtick** on macOS or **Ctrl + backtick** on Windows and Linux to focus the terminal. Use its toolbar to create another session, split the current session, or choose an installed shell. Hiding the panel keeps its processes running. Close a session when you want to stop its shell. Check the terminal prompt before running a project command. A shell in an [SSH workspace](remote-workspaces.md) runs on the remote host. ## Review and commit changes 1. Open **Source Control** and select the repository you want to work on if the workspace has more than one. 2. Open a file under **Changes** to inspect its diff. The working tree comparison uses the saved file on disk, so save the editor tab if you want to review its current text. 3. Stage the files you intend to commit, then check the staged list. 4. Enter a commit message and commit. Devyy uses the Git identity and hooks configured for the repository. Use **History → Open commit graph** to see commits and their changed files. Opening a historical diff is a read-only operation. Use the terminal for workflows that the panel does not expose, such as resolving a merge conflict. --- Source: https://www.devyy.dev/docs/extensions/ Markdown: https://www.devyy.dev/docs-markdown/extensions.md # Extensions and settings import Open **Settings → Extensions** to search Open VSX and manage installed packages. You can also install a local `.vsix` from a source you trust. ## Install and verify an extension 1. Search by publisher and extension name in **Extensions**. 2. Open the matching entry and confirm the publisher before installing. 3. Check the **Installed** list for status or activation errors. 4. Open a file in the extension’s target language and try the feature you installed it for. Devyy can use contributions such as TextMate grammars, snippets, themes, and file associations. Some extensions also run JavaScript using the Devyy extension host, which requires **Node.js 20 or later** on the desktop app’s PATH. Check `node --version`, restart Devyy after making PATH changes, and recheck the extension’s status. Devyy implements a subset of the VS Code extension API. An extension can appear in the registry and still rely on unsupported workbench APIs. Check the activation error before troubleshooting the feature itself. Extension code runs with your user account’s permissions. ## Configure a language server Open **Settings → Language servers** to see detected servers and add a manual configuration. A language server can supply features such as go to definition, formatting, and diagnostics independently of a theme or syntax grammar. If a command cannot be found, make sure the language server is installed and visible on the app’s PATH. Manual settings take priority over detected configurations. ## Import preferences In **Settings → Setup & import**, choose a detected editor and review the proposed changes. Devyy can import compatible editor, appearance, saving, terminal, and global shortcut settings. It leaves the original settings files untouched. Suggested extensions still need to be installed separately. --- Source: https://www.devyy.dev/docs/coding-agent/ Markdown: https://www.devyy.dev/docs-markdown/coding-agent.md # Use the coding agent Devyy has a built-in agent in the right sidebar. Configure a provider in **Settings → AI providers** before starting a conversation. The setup depends on the provider. For example, ChatGPT uses an account authorization flow, while an API provider can require credentials and a model selection. ## Ask about a file 1. Open a project, then open the agent sidebar. 2. Select your configured model and start a new conversation. 3. Attach a file or selection for context. Inspect the attachments before sending, especially if the file contains credentials or private data. 4. Ask a specific question, such as “Where does this function handle an empty input, and what behavior should a test cover?” An attached file is shared with the configured provider. If you switch providers, review what context the conversation will send. ## Choose workspace access | Access | What it allows | | --- | --- | | Attachments only | Use the context you explicitly include in the conversation. | | Read workspace | List, search, and read eligible saved files in the current project. | | Full workspace | Request broader file access and propose changes, subject to the provider integration and the workspace grant. | These grants are scoped to the current workspace session. Start with attachments for questions about one file and use read access when the answer depends on several files. Use the access control in the agent toolbar to change or revoke a grant. ## Review and save a proposed edit Use **Review diff** to inspect the proposal. **Apply to editor** puts it in an unsaved buffer. Check the result, then save it using the normal editor command. If the file changed since the proposal was created, request a fresh proposal before applying. AI code suggestions are a separate editor preference. You can use agent chat with AI completions disabled. --- Source: https://www.devyy.dev/docs/remote-workspaces/ Markdown: https://www.devyy.dev/docs-markdown/remote-workspaces.md # Remote workspaces over SSH Use **Remote Explorer** when the project files and tools live on another machine. You need a reachable SSH server, an account on that server, and access to the remote project directory. ## Add a server 1. Open **Remote Explorer** and choose **Add server**. 2. Enter the host, SSH port, username, and project directory on the remote host. Port `22` is conventional unless your SSH server uses a different port. 3. Choose password or private-key authentication and provide the corresponding credential. 4. Connect. Compare the host fingerprint with a trusted value from the server administrator before accepting it. Investigate unexpected changes before proceeding. Once connected, open a file and verify the remote path in the project tree. Files, terminal sessions, and Git operations in the workspace use the remote host. Install project tooling on that host if the remote terminal cannot find it. ## Forward a remote service Start the service in the remote terminal. For example, if it listens on port `3000` on the server, add a forward with **Remote port** set to `3000`. Choose a free **Local port**, such as `3001`, then visit `http://127.0.0.1:3001` on your computer. If the SSH connection works but the page does not open, check that the service is running on the configured remote port and that the local port is free. Stop the forward when you no longer need it. ## Share a local service with a Devyy address Use the editor’s **Ports** panel to publish a local HTTP or HTTPS service at an address such as `https://.devyy.xyz`. The editor manages the forward through `api.devyy.dev`. For a **Private** forward, open the address in a browser already signed in to the owning Devyy account at [www.devyy.dev](https://www.devyy.dev). Public forwards can be opened without an account.