Open Saved Links and Files Without Leaving Your Vault

A saved memory often contains the exact thing you need next: a documentation URL, a repository path, a Markdown plan, or the configuration file behind a decision. Until now, following that reference could interrupt the work you were trying to continue. A normal click might hand the whole window to a link, leave you staring at an unusable page, or force you to copy a path and hunt for it manually.

That friction is especially costly when your vault is acting as the connective tissue between projects. You are not opening a random link; you are moving from remembered context to the source that lets you act. The transition should keep the memory visible, respect the kind of target you clicked, and let you decide what happens next.

What changed

Link and File Actions now gives you a safe action menu whenever you click a URL or file path in memory details. You can open a web link in your default browser, reveal a local file in Finder or File Explorer, open supported text and source files in 1DevTool or your default code editor, or copy the original value without taking 1AIVault away from your vault.

How it works in practice

Keep the memory open while you follow a web reference

Click a web URL inside a saved conversation or memory. Instead of navigating the 1AIVault window to that address, the app opens a menu with Open in default browser. Choose it and your browser handles the page while the vault remains exactly where you left it.

That separation matters when you are checking documentation against a past decision. You can read the external page, return to the same memory, and continue through the rest of its context without reconstructing your place. The vault stays a stable workspace rather than becoming a temporary browser tab.

The app also blocks unhandled navigation as a safety net. Even if a malformed anchor does not follow the expected path, it cannot replace the vault document. You keep control of the desktop window and choose whether the link belongs outside it.

Move from a remembered path to the real file

Click a local path and choose Reveal in Finder, Reveal in File Explorer, or Show in File Manager, depending on your operating system. 1AIVault resolves the path and reveals the file on disk. If the exact target no longer exists but its parent directory does, you can still land near the location and investigate what changed.

This is useful when a memory records where a design document, source file, exported model, or configuration lived. You do not need to select the path, remove an @ prefix, open a terminal, and type a platform-specific command. The remembered reference becomes a direct bridge to the local filesystem.

Open working files in the tool that fits the task

When the target is an existing Markdown, text, source, or configuration file, the menu adds Open with 1DevTool and Open with default code editor. Choose 1DevTool when you want its focused file tools, or use your configured editor when you are ready to change the source.

1AIVault checks that the target exists and is a supported file before showing these actions. It also detects 1DevTool from normal application and command locations on macOS, Windows, and Linux. If 1DevTool is not available, the menu keeps the option disabled rather than pretending the launch succeeded.

Copy the exact value when you need it elsewhere

Choose Copy to place the original URL or path on the clipboard. This is the quiet fallback that keeps the workflow flexible: paste the value into a terminal, issue, message, or another AI tool without changing it first.

The menu reclassifies the target in the privileged desktop process instead of trusting a label supplied by the visible page. For you, the result is simple: browser actions apply to browser URLs, file actions apply to paths, and the vault never turns a click into an unexpected navigation.

Let unattended classification reach the vault again

This release also repairs scheduled Claude Code classification. When a schedule runs without you at the keyboard, Claude Code can locate the required memory tools and save its classifications back to the vault. You do not need to rerun missed schedules manually or wonder whether an unattended pass silently lost access.

Before vs After

Task	Before	Now
Follow a documentation link	Risk replacing the vault window or copy the URL manually	Choose Open in default browser and keep the memory open
Locate a remembered file	Copy the path, open a file manager, and navigate by hand	Choose the platform-specific Reveal action
Edit a referenced source file	Find the file again, then launch an editor separately	Choose Open with 1DevTool or Open with default code editor
Reuse a path in another tool	Select the exact text and hope formatting does not change it	Choose Copy from the same action menu
Run scheduled classification	Check whether Claude Code could still reach vault tools	Let the repaired schedule classify and save unattended

Who benefits most

Developers who save paths alongside decisions can jump from the reason behind a change to the exact file that implements it. The memory remains visible while the editor opens, so you do not lose the constraint or tradeoff you were trying to honor.

Researchers and operators who collect documentation URLs can inspect external references without turning 1AIVault into a browser. That makes a long memory easier to work through one source at a time.

Anyone using scheduled Claude Code classification gets a more dependable background workflow. Fresh memories can be organized even when the job runs unattended, and the results are available when you return.

Try it

Open a memory that contains a URL or local path, click the reference, and choose the action that matches what you want to do. You keep the vault in place while the link, file manager, editor, or clipboard takes over only the next step.