sharenow

Hosting for the things your agent makes.

A site, a document, a folder of work. One command, and it is live in seconds at sharenow.today.

---

There is a moment, right after an agent finishes something, where the work has nowhere to go. sharenow is the place it goes. Tell the agent to publish, and a file, a folder, an app, or a report becomes a URL someone can open. Tell it to keep something private, and that work persists in a Drive across sessions and tools, shared only with whom you choose.

No console is required for the first publish. sharenow is a skill: a small set of scripts an agent reads once and then drives on its own. A first-party browser page appears only when the user chooses to connect an account.

Two capabilities, one install.

• Sites. Publish HTML, apps, documents, images, PDFs, and video to a live URL at {slug}.sharenow.today, or a domain of your own. Three steps underneath, one command on the surface.
• Drives. Hold private agent files in cloud folders that outlast a single conversation: context, memory, plans, research, assets. Hand them to another agent with a scoped token, never a public link.

The skill carries three helpers the agent uses directly. publish.sh for Sites, drive.sh for Drives, and account.sh for the rest: Site Data, profiles, custom domains, handles, links, service variables, analytics, browser connection, and key revocation.

Install

Why security scanners may warn

Publishing skills can look powerful to automated scanners because their job is to read local files and upload them. This package contains only three shell helpers, all shown below. They send the exact files you approve to the fixed first-party origin https://sharenow.today; they do not execute downloaded content, inspect unrelated folders, or read SSH, cloud, or shell-history files. Account connection happens on a first-party browser page, so an email code or API key never needs to be pasted into an agent chat.

The publish helper automatically excludes Git metadata, sharenow private state, and node_modules. It fails closed when a target contains .env or a common private-key file type.

You can verify every installed byte against the signed-in-independent manifest at sharenow.today/.well-known/sharenow-skill.json. The higher-blast-radius collaboration and codebase-upload experiments remain outside the installed package.

One skill, the same three scripts, wherever your local agent runs. Re-run the same command later to update it in place.

Universal (recommended). Anywhere the skills CLI runs:

npx skills add AsyncFuncAI/sharenow --skill sharenow -g

Drop the -g for a project-local, repo-pinned install.

The installer discovers Codex, Claude Code, Cursor, OpenCode, and other common local-agent skill folders. If your agent does not support local shell tools, such as a browser-only chat, ask it to use sharenow's public HTTP API instead. It can publish as long as it can call curl to an external service.

After setup, try one of these directly in your agent:

• Publish this website to sharenow.
• Turn this result into a simple page and publish it to sharenow.
• Summarize this session as a shareable page and publish it to sharenow.

Manual agent-specific layouts are kept in this repository for maintainers and troubleshooting, but they are not a second install path for normal users.

What is in the package

sharenow/
├── SKILL.md            the agent-facing skill manifest
├── AGENTS.md           the operating guide for the agent
├── assets/logo.svg
└── scripts/
    ├── publish.sh      publish and update Sites (create, upload, finalize)
    ├── drive.sh        private Drive storage and scoped-token sharing
    └── account.sh      browser connection, Site Data, profiles, domains,
                        handles, links, variables, analytics, and key revocation

Every other install path in this repo (skills/, hermes/, the plugin manifests) is generated from sharenow/. That directory is the single source of truth.

Advanced channel and local-codebase Knowledge Base helpers are preserved under extras/advanced-scripts/ for future security review. They are not part of the installed skill.

Layout

Path	Surface
sharenow/	Canonical skill (edit here)
skills/sharenow/	npx skills add layout
hermes/productivity/sharenow/	Hermes layout
.codex-plugin/plugin.json	Codex manifest
.cursor-plugin/plugin.json	Cursor manifest

For maintainers

The skill lives once, in sharenow/. Edit there, regenerate the per-agent layouts, and verify before pushing:

scripts/build-layouts.sh        # regenerate skills/ + hermes/; sync the logo into
                                #   the manifest dirs (the plugin JSON is hand-authored)
scripts/verify-package.sh       # gate: paths, layout sync, lint, exec bits,
                                #       brand, manifest JSON, install-cmd consistency

build-layouts.sh --check fails the moment a generated layout drifts from the canonical source, so the copies cannot quietly fall out of step.

License

MIT. See LICENSE.