Open in IDE

Jump straight to any file in your preferred code editor — at the exact line you need — without leaving the Yukkai conversation.

What is it?

Open in IDE is a Yukkai tool that opens a file directly in your preferred code editor (IDE) at a specific line number. Instead of manually navigating folder trees or scrolling to find the right spot, you can ask Yukkai to open the file exactly where it matters — for example, the line where a bug was detected or a function needs updating.

Supported editors include Xcode, VS Code, Cursor, Zed, and Nova.

How it works

When you ask Yukkai to open a file in your IDE, the tool:

Takes the file path (required) — the location of the file on disk.
Optionally takes a line number — the editor will place your cursor on that line.
Optionally takes an ide parameter — to override the default editor for this call.

If no IDE is specified, Yukkai uses your preferred IDE (the one configured as your system default).

How to use it

You don't need to call the tool manually — simply ask Yukkai in natural language:

Open the file where the crash happens
Open line 42 of AppDelegate.swift in Xcode
Show me the bug in my ViewController in VS Code
Open the file we just edited, at the line with the error

Yukkai figures out the file path and line number from context, then launches your editor.

Parameters

Parameter	Required	Description
`path`	✅ Yes	Absolute or relative file path to open
`line`	❌ No	Line number to jump to (opens at top of file if omitted)
`ide`	❌ No	Editor to use: `xcode`, `vscode`, `cursor`, `zed`, or `nova`

Examples

Open a file at a specific line

Open line 128 of /Users/me/Projects/App/Sources/NetworkManager.swift in Xcode

This launches Xcode and places the cursor on line 128 of NetworkManager.swift.

Open a file without specifying a line

Open /Users/me/Projects/App/Package.swift in VS Code

VS Code opens the file with the cursor at the top of the file.

Let Yukkai decide

Open the file where you found the memory leak

Yukkai identifies the relevant file and line from the current conversation, then opens it in your default IDE.

Switch editors for one call

Open line 50 of main.swift in Cursor

Even if your default IDE is Xcode, this call forces the file to open in Cursor instead.

Tips & best practices

Use absolute paths when possible. Relative paths work, but absolute paths guarantee Yukkai finds the right file regardless of the working directory.
Ask in plain English. You don't need to know the exact path or line number — Yukkai can infer them from context. For example, after a code review, just say "open the file with the warning."
Mix and match editors. You can open different files in different editors. For instance, open Swift files in Xcode and config files in VS Code, all within the same conversation.
Great for debugging. When Yukkai identifies a bug at a specific line, ask it to open that exact location so you can fix it immediately — no searching required.
No IDE parameter needed for everyday use. Only specify the ide parameter when you want to override your default editor for a single call.