Take Me There

Take Me There Skill

Open the file (and line, when known) most relevant to the current conversation context in the user's preferred editor, reusing the existing window when possible.

Editor detection — in this order

1. $VISUAL if set and on $PATH.
2. $EDITOR if set and on $PATH.
3. code-insiders if on $PATH.
4. code if on $PATH.
5. cursor if on $PATH.

If none of these are available, tell the user and stop. Don't fall back to a non-GUI editor.

Open command

The supported editors all accept the same flags:

<editor> -r -g "<file>:<line>"

• -r reuses the current window instead of opening a new one.
• -g "<file>:<line>" opens at the specified line.

If $VISUAL or $EDITOR resolves to an editor that uses different syntax, use that editor's documented invocation.

Determining what to open

If the user provides a specific file and line via $ARGUMENTS, use those. Otherwise, determine the most relevant file and line from conversation context — for example:

• A recent edit you just made.
• A file/line referenced in a code review comment.
• A symbol mentioned in the last few turns.

When ambiguous, ask the user which file they meant before opening.

Why this matters

Jumping straight to a precise line in the editor often beats reading a code excerpt in chat — the editor handles syntax, scrollback, and surrounding context better than a chat client does. Especially valuable for users who navigate code with a screen reader, since editors expose code structure (symbols, sections, indentation) more reliably than chat output.