The IDE that ships the app.

Piye is built on Electron, React, and Monaco, and Piye owns every line of its interface. It is not a VS Code fork and does not try to look like one. What you get on day one, with no extensions: TypeScript and JavaScript language services, a real terminal, Git, search, debugging, testing, a ports view, Docker status, simulators, deploy, and an agent that can use all of it.

If you come from Cursor, Zed, or VS Code, the editor will feel familiar within minutes. The difference is everything around the editor.

Panels can be resized, collapsed, and popped out into their own windows. View, Reset Workbench Layout brings everything back.

• Monaco with language services for TypeScript, JavaScript, HTML, CSS, JSON, and Markdown.
• Tabs, editor groups, and ⌘\ to split right. Join All Editor Groups to merge back.
• Breadcrumbs and an outline of symbols for the current file.
• Format on save, auto save, word wrap, minimap, and font settings under Settings, Editor.
• A Simple Browser for quick looks at docs or a local URL.

⌘⇧F searches the whole project with ripgrep and respects your ignore files. ⌘⇧H replaces across files with a preview. In the agent, identifier search and "search by meaning" are available as tools.

• Compare with Saved and Compare with Clipboard from the File menu.
• Resolve Merge Conflicts opens a dedicated view for conflicted files.
• Agent file cards open as diffs before you accept them.

Open it with ⌘⇧A, or pop it out into its own window. Pick a mode and a model, attach files or images, and talk to your project. The agent sees what you see, so you never paste the file you are looking at: say "this" or "here" and it quotes your visible range.

Accepting a card applies the edit to the open tab and writes disk, so the tab is clean afterwards. Closed files are written to disk directly.

Each turn starts with a live snapshot of the workbench. No copy and paste needed.

At the start of every turn Piye records a checkpoint: your dirty buffers and the Git HEAD. Undo on a turn restores those buffers and reverts the file cards you accepted in it.

Put conventions the agent should follow in .piye/rules.md, AGENTS.md, or several files under .piye/rules/. They are injected into every turn, capped so they never crowd out your code.

• ⌘` toggles the panel, ⌘⇧` opens a new terminal. Split Terminal sits next to it.
• ⌘⇧T pops the terminal into its own window.
• Commands the agent runs with approval use a separate process and do not appear in your terminal. IDE actions like starting Expo write into the terminal you already have.

The Testing panel discovers tests in your project and runs them from the panel or the editor gutter. The agent uses the same commands, so "fix the failing test" means it can run it, patch, and run it again.

Run and Debug speaks the Debug Adapter Protocol. Configurations live in .piye/launch.json. Set breakpoints in the gutter, step through code, and read variables, the call stack, and the debug console.

• Problems collects diagnostics from language services. Click one to jump to the file and range.
• Tasks run your package scripts and anything in .piye/tasks.json. ⌘⇧B runs the build task.
• Output shows logs from tasks, extensions, and Piye itself.

Ports lists every listening TCP port on your machine with the process name and a local URL to open. The agent checks it before suggesting npm run dev, so you do not end up with two servers fighting over port 3000.

The Apps view has four tabs: Project, Devices, Stores, and Setup. Piye detects each app from its package.json, including nested apps/, packages/, and mobile/ folders in a monorepo.

Pin the stack with .piye/app.json to skip detection. Stores connects App Store Connect, Google Play, and EAS so you can submit builds without leaving Piye.

Deploy shows the selected host, sign-in state, the linked project, production URL, environment variable names with sync status, Docker engine status, and the build log. Deploy Now ships it.

Operations (⌘⇧O) is your production radar. It probes the services your project actually uses and streams what changed: failed deploys, CI runs, store reviews, Stripe events, new CVEs.

The header's Watching N is the number of live adapters being probed (Railway, Vercel, Hostinger, GitHub, Expo and EAS, Stripe, the stores). Operations also helps set up SEO, analytics, consent, and edge configuration by writing the code into your project.

Press Connect on a marketplace card. Piye writes the launcher into its own MCP config and runs the sign-in. No API key forms, no JSON editing.

The status bar shows the active model and route. Change the default in Settings, AI, or per conversation in the Agent panel.

Shown for macOS. On Windows and Linux, ⌘ is Ctrl. Open the full list with ⌘⇧/ and override any of them in .piye/keybindings.json.

View, Open in New Window pops out the Agent, Operations, or Terminal. Each keeps working on the same project, so you can put the agent on one screen and the code on another.

• Jupyter notebooks with real kernels from your own Python environments.
• Built-in Tailwind IntelliSense, Prettier, and ESLint without extensions.
• Inline blame, file history, and conflict resolution in Git.
• An agent task queue for running several agents in parallel.
• The OXP registry with signed packages.