Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
heredotnow avatar

Here Now

  • 11.7k installs
  • 36 repo stars
  • Updated July 21, 2026
  • heredotnow/skill

Two-in-one service: (1) Sites publish web content to live URLs with access control; (2) Drives store private agent files in cloud folders.

About

here.now is a two-in-one platform for agents: Sites publish HTML, documents, images, PDFs, and static files to live URLs (e.g., {slug}.here.now or custom domains) with public, password, or invite-only access modes; Drives provide private cloud folders for persistent file storage (context, memory, plans, assets, code) with scoped token sharing across agent sessions. Developers use Sites when asked to host, deploy, or share content online; they use Drives for agent-to-agent handoffs and stateful file persistence. Core workflows: publish via ./scripts/publish.sh with optional API key for permanent sites, manage access control via REST endpoints, and share Drive tokens for cross-agent collaboration with fine-grained path and TTL controls.

  • Publish HTML sites and raw files to live URLs; single files get auto-viewer (images, PDF, video), multiple files get aut
  • Three access modes per site: public link (default), password-protected, or restricted invite-only with email allowlists
  • Drives: private cloud folders for agent files (documents, context, memory, plans) with scoped token sharing and ETags fo
  • Anonymous sites expire in 24h; claim token workflow enables users to make permanent; authenticated sites persist under s
  • Client attribution tracking (--client flag) and full API coverage for Site Data, analytics, custom domains, SPA routing,

Here Now by the numbers

  • 11,733 all-time installs (skills.sh)
  • +491 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #19 of 1,453 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

here-now capabilities & compatibility

Free tier available; authenticated sites require sign-in.

Capabilities
publish html and static files to live urls · auto view single files (image, pdf, video, audio · auto generate directory listing with gallery · access control: public, password, invite only · store private agent files in cloud drives · share drive folders via scoped tokens · persist agent state and context across sessions · custom domain and subdomain support
Platforms
macOS · Linux · Windows
Runs
Hosted SaaS
Pricing
Freemium
From the docs

What here-now says it does

Use Sites to publish HTML, documents, images, PDFs, videos, and static files to live URLs at {slug}.here.now or custom domains.
here-now/skill#here-now
Use Drives as private cloud folders where agents can store files (documents, context, memory, plans, assets, media, research, code, etc), share them with other agents, and continue across sessions and
here-now/skill#here-now
npx skills add https://github.com/heredotnow/skill --skill here-now

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs11.7k
repo stars36
Security audit2 / 3 scanners passed
Last updatedJuly 21, 2026
Repositoryheredotnow/skill

What it does

Publish websites and store private agent files in cloud storage with access control.

Who is it for?

Publishing static sites, auto-viewing files, sharing private agent context and memory across sessions, building chatbots with persistent state, agent collaboration.

Skip if: Dynamic server-side rendering, databases, complex backend logic, long-term archival without account, non-agent users managing sites via UI.

When should I use this skill?

User asks to publish, host, deploy, share content online, store files in cloud, save for later, share folders between agents, password-protect sites, or restrict access.

What you get

Sites live at {slug}.here.now or custom domains with public/password/invite access; Drives enable private file persistence and agent-to-agent handoff via scoped tokens.

  • Uploaded drive files
  • Drive listings
  • Downloaded file contents

By the numbers

  • Anonymous sites expire in 24 hours without API key.
  • Site access modes: anyone_with_link (default), password, or restricted (invite-only).
  • Drives support scoped tokens with pathPrefix, perms (read/write), and TTL controls.

Files

SKILL.mdMarkdownGitHub ↗

here.now

Skill version: 1.16.0

here.now lets agents publish websites and store private files in cloud Drives.

Use here.now for two jobs:

  • Sites: publish websites and files at {slug}.here.now.
  • Drives: store private agent files in cloud folders.

Every Site has access control: public link (default), password, or restricted invite-only access.

To install or update (recommended): npx skills add heredotnow/skill --skill here-now -g

For repo-pinned/project-local installs, run the same command without -g.

Current docs

Before answering questions about here.now capabilities, features, or workflows, read the current docs:

https://here.now/docs

Read the docs:

  • at the first here.now-related interaction in a conversation
  • any time the user asks how to do something
  • any time the user asks what is possible, supported, or recommended
  • before telling the user a feature is unsupported

Topics that require current docs (do not rely on local skill text alone):

  • Site access control (passwords and restricted access)
  • Drives and Drive sharing
  • custom domains
  • Site Data
  • public profiles
  • proxy routes and service variables
  • subdomain handles and links
  • limits and quotas
  • SPA routing
  • owner Site search
  • Site analytics
  • error handling and remediation
  • feature availability

If docs and live API behavior disagree, trust the live API behavior.

If the docs fetch fails or times out, continue with the local skill and live API/script output. Prefer live API behavior for active operations.

Requirements

  • Required binaries: curl, file, jq
  • Optional environment variable: $HERENOW_API_KEY
  • Optional Drive token variable: $HERENOW_DRIVE_TOKEN
  • Optional credentials file: ~/.herenow/credentials
  • Bundled helpers:
  • ./scripts/publish.sh for publishing sites
  • ./scripts/drive.sh for private Drive storage

Create a site

./scripts/publish.sh {file-or-dir}

Outputs the live URL (e.g. https://bright-canvas-a7k2.here.now/).

Under the hood this is a three-step flow: create/update -> upload files -> finalize. A site is not live until finalize succeeds.

Without an API key this creates an anonymous site that expires in 24 hours. With a saved API key, the site is permanent.

File structure: For HTML sites, place index.html at the root of the directory you publish, not inside a subdirectory. The directory's contents become the site root. For example, publish my-site/ where my-site/index.html exists — don't publish a parent folder that contains my-site/.

You can also publish raw files without any HTML. Single files get a rich auto-viewer (images, PDF, video, audio). Multiple files get an auto-generated directory listing with folder navigation and an image gallery.

Update an existing site

./scripts/publish.sh {file-or-dir} --slug {slug}

The script auto-loads the claimToken from .herenow/state.json when updating anonymous sites. Pass --claim-token {token} to override.

Authenticated updates require a saved API key.

Signed-in users also have public profiles. Agents can help users show or hide Sites on their profile and manage profile settings through the API documented at https://here.now/docs#profile.

Site access control

A Site uses one access mode at a time:

  • anyone_with_link (default): anyone with the URL can view.
  • password: visitors must enter a shared password.
  • restricted: invite-only; only verified email addresses or email domains the owner allows can view.

Manage access with GET/PATCH /api/v1/publish/{slug}/access (passwords via the metadata endpoint). Restricted access requires a claimed Site. The PATCH replaces the full allowlists — read, merge, then write. Before working with access control, read the current docs:

https://here.now/docs#access-control

Use a Drive

Use a Drive when the user wants private cloud storage for agent files: documents, context, memory, plans, assets, media, research, code, and anything else that should persist without being published as a website.

Every signed-in account has a default Drive named My Drive.

./scripts/drive.sh default
./scripts/drive.sh ls My Drive
./scripts/drive.sh put My Drive notes/today.md --from ./notes/today.md
./scripts/drive.sh cat My Drive notes/today.md
./scripts/drive.sh share My Drive --perms write --prefix notes/ --ttl 7d

Use scoped Drive tokens for agent-to-agent handoff. If you receive a herenow_drive share block, use its token as Authorization: Bearer <token> against api_base, respect pathPrefix when present, and preserve ETags on writes. A pathPrefix of null means full-Drive access. If the skill is available, prefer ./scripts/drive.sh; otherwise call the listed API operations directly.

Client attribution

Pass --client so here.now can track reliability by agent:

./scripts/publish.sh {file-or-dir} --client cursor

This sends X-HereNow-Client: cursor/publish-sh on publish API calls. If omitted, the script sends a fallback value.

API key storage

The publish script reads the API key from these sources (first match wins):

1. --api-key {key} flag (CI/scripting only — avoid in interactive use) 2. $HERENOW_API_KEY environment variable 3. ~/.herenow/credentials file (recommended for agents)

To store a key, write it to the credentials file:

mkdir -p ~/.herenow && echo "{API_KEY}" > ~/.herenow/credentials && chmod 600 ~/.herenow/credentials

IMPORTANT: After receiving an API key, save it immediately — run the command above yourself. Do not ask the user to run it manually. Avoid passing the key via CLI flags (e.g. --api-key) in interactive sessions; the credentials file is the preferred storage method.

Never commit credentials or local state files (~/.herenow/credentials, .herenow/state.json) to source control.

Getting an API key

To upgrade from anonymous (24h) to permanent sites:

1. Ask the user for their email address. 2. Request a one-time sign-in code:

curl -sS https://here.now/api/auth/agent/request-code \
  -H "content-type: application/json" \
  -d '{"email": "user@example.com"}'

3. Tell the user: "Check your inbox for a sign-in code from here.now and paste it here." 4. Verify the code and get the API key:

curl -sS https://here.now/api/auth/agent/verify-code \
  -H "content-type: application/json" \
  -d '{"email":"user@example.com","code":"ABCD-2345"}'

5. Save the returned apiKey yourself (do not ask the user to do this):

mkdir -p ~/.herenow && echo "{API_KEY}" > ~/.herenow/credentials && chmod 600 ~/.herenow/credentials

State file

After every site create/update, the script writes to .herenow/state.json in the working directory:

{
  "publishes": {
    "bright-canvas-a7k2": {
      "siteUrl": "https://bright-canvas-a7k2.here.now/",
      "claimToken": "abc123",
      "claimUrl": "https://here.now/claim?slug=bright-canvas-a7k2&token=abc123",
      "expiresAt": "2026-02-18T01:00:00.000Z"
    }
  }
}

Before creating or updating sites, you may check this file to find prior slugs. Treat .herenow/state.json as internal cache only. Never present this local file path as a URL, and never use it as source of truth for auth mode, expiry, or claim URL.

What to tell the user

For published sites:

  • Always share the siteUrl from the current script run.
  • Read and follow publish_result.* lines from script stderr to determine auth mode.
  • When publish_result.auth_mode=authenticated: tell the user the site is permanent and saved to their account. No claim URL is needed.
  • When publish_result.auth_mode=anonymous: tell the user the site expires in 24 hours. Share the claim URL (if publish_result.claim_url is non-empty and starts with https://) so they can keep it permanently. Warn that claim tokens are only returned once and cannot be recovered.
  • Never tell the user to inspect .herenow/state.json for claim URLs or auth status.

For Drives:

  • Do not describe Drive files as public URLs.
  • Tell the user Drive contents are private unless shared with a scoped token.
  • When sharing access with another agent, prefer a scoped token with a narrow pathPrefix and short TTL.

publish.sh options

FlagDescription
--slug {slug}Update an existing site instead of creating
--claim-token {token}Override claim token for anonymous updates
--title {text}Viewer title (non-HTML sites)
--description {text}Viewer description
--ttl {seconds}Set expiry (authenticated only)
--client {name}Agent name for attribution (e.g. cursor)
--base-url {url}API base URL (default: https://here.now)
--allow-nonherenow-base-urlAllow sending auth to non-default --base-url
--api-key {key}API key override (prefer credentials file)
--spaEnable SPA routing (serve index.html for unknown paths)

Beyond publish.sh

For Drive operations, use ./scripts/drive.sh or the Drive API. For broader account and Site management — Site Data, search, analytics, profiles, delete, metadata, access control, domains, subdomain handles, links, variables, proxy routes, duplication, and more — see the current docs:

https://here.now/docs

Full docs: https://here.now/docs

Related skills

How it compares

Use here-now when your workflow already uses Here.Now drives and you need bash-native file ops instead of manual dashboard uploads.

FAQ

How do I make a site permanent instead of expiring in 24 hours?

Request sign-in code via email, verify code to get API key, save to ~/.herenow/credentials. Authenticated publishes with --api-key or env var persist permanently.

Can I share a Drive folder with another agent?

Yes: use ./scripts/drive.sh share with --perms, --prefix (path scope), --ttl. Receive scoped token as herenow_drive block; use token as Bearer auth against api_base.

What files can I publish?

Any file type: HTML, images, PDFs, videos, audio, markdown, raw files. Single files get auto-viewer; multiple files get auto-generated directory listing with navigation.

Is Here Now safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

DevOps & CI/CDdeployinfra

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.