You're reviewing a markdown file someone sent you, or you just downloaded a JSON response you want to inspect. You double-click the file in Finder. It opens in your system's default editor — probably TextEdit, Notes, or VS Code — which is probably not where your active project is or where your AI terminals are running.

Getting the file into 1DevTool meant dragging it manually, using the file tree, or copy-pasting the contents in. A small friction, but it interrupts the flow every time.

Open Files from Your OS Directly into the Workspace

You no longer have to drag files into 1DevTool. Set 1DevTool as the default app for .md, .txt, .json, .yml, and .yaml files, and double-clicking opens them straight into your workspace. The file appears in the editor, inside the right project, ready to edit or send to an AI agent.

1DevTool also handles the project question automatically: if the file lives inside an existing project folder, it switches to that project. If not, it creates a new project from the file's parent folder on the spot.

How It Works in Practice

Double-click → straight into your workspace

After setting 1DevTool as the default for supported file types (right-click → Open With → Set as default in Finder, or the equivalent in Windows Explorer), opening any .md, .json, .yml, or .txt file from the OS routes it directly into 1DevTool's editor.

There's no separate "import" step, no dialog to navigate. The file opens where you'd expect it to — in your editor panel, in whatever project it belongs to.

The right project opens automatically

If the file you opened lives inside a folder that 1DevTool already knows as a project, 1DevTool switches to that project before opening the file. You land in the right context without manually navigating.

If the file's parent folder isn't a project yet, 1DevTool creates one from it. You can start editing immediately and the project persists for next time.

Terminals under each project in the sidebar

The same release adds a toggle to the Projects section that reveals visible terminals directly under their project in the sidebar. When you have multiple projects open with multiple AI terminal sessions running, this gives you a map: which project has active work, and which terminal is running in it.

Click a terminal row in the sidebar and the terminal panel focuses and switches to that session. You no longer have to remember which terminal you left something in — you can see it at a glance.

Before vs After

Task	Before	After
Open a `.json` file from Finder	Opens in TextEdit or VS Code	Opens in 1DevTool editor, in the right project
Open a file from an existing project	Drag into 1DevTool, navigate file tree	Double-click → jumps to project and opens
Open a file from a new folder	Drag, create project manually	Double-click → project auto-created
Find which terminal is running what	Check each terminal panel	Terminals listed under projects in sidebar
Jump to a specific terminal	Click through terminal tabs	Click the terminal row in the sidebar

Who Benefits Most

Anyone who handles a lot of files outside their editor — If you regularly get Markdown docs, JSON payloads, or YAML configs from email, Slack, or downloads, the default-app change eliminates the step of manually bringing those files into your workspace.

Developers with multiple active projects — When you have five projects open and a dozen AI terminals running, the terminal sidebar gives you a layout overview without clicking around. You can see at a glance which project has an active agent session and jump there directly.

Teams reviewing files together with AI — Opening a file from Finder and immediately having it inside a project next to your AI terminals makes the "review this file with the agent" workflow a single gesture instead of several.

Try It

In Finder, right-click a .md or .json file, choose Open With, select 1DevTool, and check "Always Open With." From then on, double-clicking those files routes them into your workspace. For the terminal sidebar, look for the toggle in the Projects panel header — flip it on and your active terminal sessions appear under each project.