Major Release: Moment v1.5 with wikilinks, workflows, cloud secrets and more

Every release of Moment starts the same way: in our inbox, in customer calls, in Discord threads with teams who are actually using the product every day.This version is no exception. Every feature in this release traces back to something you asked us for, usually more than once, often with a very specific use case attached.

Available in public beta today, Moment v1.5 is a substantial release and is our latest step toward that vision. We're building Moment to be the ultimate workflow tool for development teams: one place where the runbooks, dashboards, queries, scheduled jobs, and tribal knowledge that actually run your engineering org all live together — versioned, executable, and connected. Not a wiki bolted to a notebook bolted to a cron. A single surface where writing a doc, querying production, and scheduling an agent to keep both fresh are the same motion.

Here's what's new:

Wikilinks: Connect any two pages with [[double brackets]] and turn your workspace into a navigable knowledge graph.

Workflows: Cron-scheduled jobs that run shell scripts or AI coding agents against a Moment document, so your docs and dashboards refresh themselves while you sleep.

Import from folder: Point Moment at an Obsidian vault or docs/ directory and get a fully linked Moment document — folder hierarchy and wikilinks intact — in seconds.

Attachments: Drop CSVs and SQLite databases onto a document and query them directly from request pages and code cells.

Improved environments: Per-user variables, workspace-wide secrets, and a direct AWS integration — all referenced with {{env.NAME}} and held in a Rust proxy so credentials never touch your Markdown.

Human-readable slugs: Page folders and URLs are now derived from page titles, so file trees, git log, and shared links all read like English instead of random IDs.

Wikilinks

Wikilinks let you turn any note into a hub of connected ideas using [[double brackets]] right in the editor. Type [[ anywhere in a Moment document and an autocomplete menu of existing notes appears. Keep typing to filter, hit Enter to insert the link. Reference a note that doesn't exist yet, and clicking the link later spins up a new document with that title — so emerging concepts like [[2026 Platform GTM]] never break your writing flow.

As your workspace grows, wikilinks turn scattered pages into a navigable knowledge graph: meeting notes point to strategy docs, docs point to specs, specs point back to decisions. The graph becomes a set of organic trails through your team's thinking.

Wikilinks also compose with the new Import from Folder feature — [[...]] patterns in imported Markdown are resolved to internal Moment links automatically, so an Obsidian vault keeps its link graph on import.

Workflows

Workflows are scheduled jobs that run inside Moment — think of them as cron for your documents. A Workflow fires on a cron schedule you define, runs either a shell script or an AI coding agent (Claude, Amp, Codex, or Copilot), and targets a specific Moment document as its working context.

If you've ever wanted your document to refresh itself every weekday morning, open a PR when a metric drifts, or have Claude reconcile last night's build logs before you sit down with coffee — that's a Workflow.

Combined with Moment KM, Workflows are what make the knowledge base living rather than static. You can schedule nightly ingest passes, weekly lint runs to find stale pages or broken cross-links, or hourly refreshes of a dashboard that lives alongside its runbook. The "agents that maintain your wiki while you sleep" promise of the LLM Wiki pattern is literally a cron expression away.

⭐️Read more: Building workflows

Import from folder

Most of the useful writing in your life already exists. It's in a notes/ folder, an Obsidian vault, a docs/ directory in some repo, a research dump you've been accumulating for years.

Import from Folder is the shortest path from that pile of Markdown on disk into a navigable Moment document. Open the New Document dropdown in the top right, choose Import from Folder, pick a folder anywhere on your disk, and Moment:

Recursively descends the entire tree.

Scoops up every .md file at any depth.

Creates a new Moment document that mirrors the original folder hierarchy exactly.

Resolves [[wikilinks]] to internal Moment links along the way.

Point it at an Obsidian vault, a Zettelkasten, or your repo's docs/ folder and you're reading, editing, and cross-linking inside Moment within seconds. The feature is labeled Beta while we refine edge cases around very large folders and attachments, but it's the single fastest way to move an existing knowledge base into Moment.

Attachments

⭐️Read more: Working with attachments

Cloud Secrets

The other half of building real internal tools is credentials. A dashboard that hits production needs a different token than the one that hits staging, and neither token belongs in a Markdown file. Environments are how Moment handles this: named bundles of values — environment variables, workspace secrets, and AWS integrations — that you switch between from the environment selector in the top right.

Every value is referenced with Mustache syntax like {{env.GITHUB_TOKEN}} in request pages and fetch calls. The actual secret never reaches your JavaScript. A built-in Rust proxy holds the credential and splices it in at the network layer, on the way out — so a screenshot, a console log, or a shared .moment directory only ever contains the placeholder.

Moment v1.5 now includes three flavors that cover common cases:

Local Secrets are per-user and per-environment. Your GITHUB_TOKEN is yours; your teammate has their own. Stored encrypted at rest, materialized only inside the proxy.

Cloud Secrets are environment variables shared across the workspace, for team-wide service accounts and shared backends. Same {{env.NAME}} syntax — a page does not need to know which kind a value came from.

Integrations are long-lived credential bundles that do not fit the simple key-value model. AWS is the first: sign in via SSO from the environment selector, and the proxy signs outbound calls with SigV4 on your behalf. Construct AWS SDK v3 clients with env._aws.region and env._aws.credentials from a JavaScript request page — no access keys to paste, nothing to rotate by hand. Kubernetes and other Globals are on the way.

The architectural payoff is that you can commit a whole document — request pages, code cells, dashboards — and a teammate can run it against their own environment without ever seeing yours. The Markdown is shareable; the credentials stay in the proxy.

Human-readable slugs

Before today, every page you created in Moment lived in a folder named with a pseudo-random 25-character identifier:

Now, page slugs become human-readable by default, derived from the page title. A page called "Blog Post [DRAFT]" now lives at pages/blog-post-draft/index.md, with a matching URL.

That means:

Legible file trees. Opening a Moment document in your editor reads like a table of contents.

Meaningful git history. git log shows pages/press-release-draft/index.md instead of an opaque ID.

Shareable URLs. Links you paste into Slack or email convey what they point to before anyone clicks.

Better agent ergonomics. Claude Code and other agents can navigate a document by topic rather than by guessing which random ID maps to which page.

Every page still has a stable underlying id, so rename-and-link never breaks. The slug is purely the human-facing handle.

Get started

Moment v1.5 is available today in public beta for all Moment.dev users. If you're tired of chatting with amnesiac wikis and want to see your team's knowledge actually compound, come download the desktop app.