How Beynt works

What Beynt is

Beynt groups your work into collections called stacks. You can add to a stack yourself or let a connected AI app save there, then find any item by title, content or tag.

Tip: a stack is a whole collection, not a single file. A folder with fifty notes is one stack with fifty artifacts.

Your first five minutes

1. Create a stack. In the sidebar, next to Stacks, choose + New, type a name and press Enter.
2. Save your first artifact. Open the stack, then choose New Artifact at the top and pick a type, or press a shortcut: N note, C command, Q query, G config, P prompt.
3. Give it a clear title. Write it the way you would search for it later, such as “Restart the web server” rather than “command 3”. Tags are optional.
4. Find it again. Press Ctrl/⌘ + K and type a word from the title or the content.
5. Copy it. Every card has a copy button, so the content is ready to paste into your terminal, editor or chat.

Already have notes somewhere else? Skip ahead to bring your notes.

Put your most-used stacks first: drag a sidebar handle, use ↑/↓ while it is focused, or choose Move up / Move down in the stack menu. Your order saves automatically within each group, including read-only shared stacks. Clear the sidebar search before reordering.

Which type to choose

The type decides how the artifact is shown and copied. If in doubt, choose Note.

Beynt stores and shows your commands and queries; it never runs them.

Find and reuse

• Home shows your most recently updated artifacts, with a copy button on each.
• Search (Ctrl/⌘ + K) finds titles and content across the stacks you can open. Use type and tag filters to narrow the results.
• Values to fill in. Write {{release_tag}} or ${HOST} where a value changes each time. When you copy, Beynt asks for the values and shows a preview. Choose Copy original to keep the placeholders.
• Code inside notes. Each code block has its own Copy button. Use Fill & copy for placeholders: values can be reused across blocks until you close the note, or removed with Clear values. Your saved note stays unchanged.
• Long notes. Open On this page to jump between sections in notes with several headings.
• Direct links. Choose Copy link in the artifact menu to return to it later or send its address to someone who already has access to the stack.
• Content, Details and Comments. Open an artifact to read its content, inspect its metadata and keep technical notes or discussion in the Comments tab.
• History. Use History in the artifact menu to browse saved revisions; load more when needed. Restoring creates a new revision and keeps its source visible. Older unverified revisions are pruned by retention; the current and verified revisions are protected.

Press ? anywhere in the workspace to see all keyboard shortcuts.

Folders and links

A stack can hold a whole folder of Markdown notes, such as a knowledge base or a project’s documentation, without creating a stack for every file.

• Path. Give a note a path such as guides/setup.md. The part before the last slash is its folder. Paths are optional and unique within a stack.
• Links in the text. In a note, [Setup](guides/setup.md) links to another note by path, and [Setup](guides/setup.md#install) links to one of its headings. [[Setup guide]] links by title.
• Links you add yourself. Open an artifact and select the Links tab. Use Add a link at the top to search for another artifact and choose how they relate: related, depends on, part of or supersedes. Existing connections and references to this artifact appear below. Links inside a note remain directly clickable in Content.
• Four views. At the top of a stack, Grid shows cards and List shows compact rows; both follow the type tabs. Index groups artifacts by folder and lists unresolved links. Graph shows artifacts and their connections: find a title or path, focus its neighbors, filter relations or use Link mode to connect two artifacts.

Tip: after changing a note’s path, update Markdown links that use its old path. After changing its title, check wikilinks that use the old title. Manual links keep pointing to the same artifact; access still depends on its stack.

Bring your notes, take them with you

Every stack has a menu: the ⋮ button next to its name in the sidebar.

• Import folder… Choose a folder, some .md files or a .zip. Each Markdown file becomes a note at its path, and the title comes from its first # heading. Before anything is saved you see a preview: new, updated and skipped files, and the links that won’t resolve.
• Import it again whenever you like. Only files that changed are updated. Nothing in Beynt is deleted, and notes you edited in Beynt after the preview are left alone.
• Download as folder (.zip) downloads the current content of a stack as files, keeping the paths you assigned. Artifacts without a path receive a generated filename. Open and edit the files in your own tools, without needing Beynt.
• Export Markdown downloads the whole stack as a single readable document. The same action in an artifact’s menu downloads just that artifact.
• Import at the bottom of the sidebar accepts collections in the Beynt JSON format. Use its help panel for the structure and examples. Oversized or invalid artifacts are reported as skipped; their content is never silently shortened.

What exports include. The current saved content of every artifact type: commands, queries, configs, prompts and notes. Comments, revision history, tags, manually added relationships, verification records and sharing settings are not included.

Images, HTML files and hidden folders such as .git or .obsidian are not imported. Each import takes up to 500 files and 8 MB; import a large collection one subfolder at a time.

Share a stack

Your stacks are private until you share them. From the stack menu choose Share and invite people by email, even if they don’t have an account yet.

• Read-only lets them open, search and copy.
• Can edit also lets them add and change artifacts.

Shared stacks appear in their sidebar under Shared by your name. You can change or remove access at any time; your other stacks stay private.

Mark what you tested

For commands, queries and configs you can record that a version works: choose Mark verified in the artifact’s menu. Note where you tried it (for example “PostgreSQL 16”) and, if you like, what you checked.

Verification belongs to that exact version. When the content changes, the new version starts unverified, so Verified always refers to the text you are looking at. Beynt never marks anything as verified on its own. Notes and prompts are not verified.

Connect an AI agent

Beynt works with AI apps that support MCP, such as Claude, Cursor, Codex, VS Code and Windsurf. A connected agent can search your stacks, read notes and, if you allow it, save what you worked out together.

1. In the workspace, choose Connect an agent at the bottom of the sidebar.
2. Pick your app, the stacks it may use, and whether it can only find references or also save them.
3. Copy the setup into your app, then send it: “List my Beynt stacks.”

When you ask an agent to save something, ask it to include the result, why you chose it and what is still open. The note will still make sense weeks later, without the original chat.

An agent reads a stack like a folder: it lists the paths, opens a note, jumps to one section and follows its links. An agent can also propose a change instead of saving it: the proposal waits on your Home until you accept or reject it.

Start note. Choose Set as start note in a note’s menu, or Choose start note in the Start here panel at the top of a stack. Pick the note with the goal, current decisions and conventions: connected agents are asked to read it before working in that stack.

Access lasts 90 days and you can disconnect an app at any time from Settings → Manage access.

Privacy and good habits

• Keep secrets out. Don’t save passwords, API keys or tokens in artifacts. Use a {{placeholder}} instead. Beynt warns you when something looks like a credential, and the folder import skips files that contain one.
• One idea per artifact. Short, well-titled artifacts are easier to find and to share than one long page.
• Export a copy. Download a stack as a folder whenever you want a copy outside Beynt. The details are in the Privacy Policy.