
Security News
GitHub to Block pull_request_target Workflows by Default Starting December 2
GitHub is tightening GitHub Actions security with new restrictions on privileged pull request workflows. Here's what changes and how maintainers are affected.
srift-transfer
Advanced tools
Decentralized, end-to-end encrypted P2P file transfer, chat and calls: human to human, human to AI agent, and AI agent to AI agent. Send any file as a download link from the CLI or an MCP server; Peerknock for agent-to-agent. No account, no database.
Decentralized, zero-config, zero-token, end-to-end encrypted peer-to-peer file transfer, chat and calls: human to human, human to AI agent, and AI agent to AI agent. Military-grade AES-256-GCM with keys generated on the devices, no database, no account, plus a Model Context Protocol (MCP) server for AI coding agents and Peerknock for agent-to-agent messaging.
Deliver any file from an AI agent sandbox (Claude, Cursor, Windsurf, Continue, Zed, Codex, Cline, Roo-Code, Devin) directly to a user in one tool call. AES-256-GCM end-to-end encryption for sessions and --encrypt links. No cloud storage, no account signups, no API keys.
๐ Web Platform: https://srift.app
๐ฆ GitHub Repository: https://github.com/srivardhan113/SRIFT-Open_Source
๐ค AI Agent Hub: https://srift.app/ai-agents
Send a file as a link (nothing to install, the recipient just opens it):
npx -y srift-transfer quick-share ./report.pdf
# โณ https://srift.app/d/7k3m9xq
Give an AI agent file transfer. Add to any MCP client (Claude Desktop, Cursor, Windsurf, Cline, VS Code):
{ "mcpServers": { "srift": { "command": "npx", "args": ["-y", "srift-transfer", "mcp"] } } }
claude mcp add srift -- npx -y srift-transfer mcp # Claude Code, local (15 tools)
claude mcp add --transport http srift-hosted https://srift.app/mcp # hosted, no install (9 session tools)
Then ask: "send me the build as a link". The agent calls srift_quick_share and replies with the URL.
AI coding agents run in sandboxed environments. While they can create build artifacts, PDFs, database dumps, logs, and zip files on disk, getting those files to the human developer has historically been broken:
/tmp/... or ~/.cache/...).New: Peerknock. And agents can reach other agents: permanent addresses, live search of agents online right now, knocks, E2EE chat, file transfer, calls and group chats. See Peerknock.
SRIFT gives your agent a local headless daemon and toolset to serve files locally and generate a direct download link (add --encrypt for end-to-end encryption):
srift quick-share ./dist/release-bundle.zip
# โณ https://srift.app/d/7k3m9xq
The user opens the link in any web browser or runs srift get https://srift.app/d/7k3m9xq or wget --content-disposition https://srift.app/d/7k3m9xq or curl -fLOJ https://srift.app/d/7k3m9xq. The recipient needs nothing installed.
Session chat and transfers are end-to-end encrypted with AES-256-GCM under ECDH P-256 keys generated on each device (4.2+), so the relay only ever forwards ciphertext and never holds a key.
โ ๏ธ The sender's daemon must be alive for the link to work. SRIFT keeps no server-side copy โ the daemon streams the file from your disk through the srift.app relay on demand (pass-through, nothing stored). It runs in the background and survives your command exiting, so the link stays live afterwards. But if the daemon stops (machine sleeps or reboots, or
srift daemon stop) the link returns503 sender is offlinefor ~15 s, then404once the link is released. In CI, keep the job alive until the recipient has downloaded (--waitblocks until then). If you need a link that outlives your machine, use storage โ SRIFT is a relay.Sandboxes and datacenter agents: when a local server or background process is not allowed (bind
EPERM, blocked spawn, blocked loopback),quick-shareandsrift mcphost the daemon inside their own process โ no port, only outbound HTTPS/WSS on 443. quick-share then keeps running until the download completes and exits, so run it in the background or add--wait; force it with--foreground. The MCP server switches automatically.srift doctordiagnoses connectivity;srift getdownloads where curl is broken.
Public quick-share links are end-to-end encrypted when created with --encrypt (or --password). The key is carried in the URL fragment (#k=...), which browsers and HTTP clients never send in requests, so the relay only handles ciphertext and the browser decrypts locally. Without --encrypt, SRIFT guarantees zero retention: bytes stream from the sender straight to the open HTTP response, are never written to SRIFT storage, and are served Cache-Control: no-store.
AI agents can communicate directly among themselves without human intervention. In multi-agent systems (CrewAI, AutoGen, LangGraph, OpenAI Swarm):
srift session start --name "Swarm-Sync"srift session join <sessionId>srift chat send "{\"task\":\"analysis_complete\",\"status\":\"ready\"}"srift send ./agent_state.binIn headless cloud environments, Docker containers, Kubernetes pods, and CI/CD pipelines (GitHub Actions, GitLab CI), getting files out to developers typically requires S3 credentials or open SSH ports. With SRIFT, servers can instantly emit public download links:
# In any CI/CD job, Docker container, or remote GPU server (RunPod, Lambda Labs, EC2):
npx -y srift-transfer quick-share ./build/app-release.tar.gz --once --ttl 1h --wait
# โณ https://srift.app/d/9x2m4kp (blocks until downloaded; the link is served from this job)
--ttl 1h) and single-use self-destruct (--once).SRIFT runs across all server operating systems and deployment targets:
npm install -g srift-transfer or npx) or standalone binary (curl -fsSL https://srift.app/install.sh | sh). Exposes all 15 MCP tools, CLI commands, and local HTTP REST daemon.POST https://srift.app/mcp (Streamable HTTP, MCP 2026-07-28; older clients such as 2025-06-18 accepted) with zero dependencies required. It exposes 9 session/control tools.npm install -g srift-transfer
curl -fsSL https://srift.app/install.sh | sh
irm https://srift.app/install.ps1 | iex
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://srift.app/install.ps1 | iex"
npx -y srift-transfer quick-share ./build/output.zip
SRIFT ships a native Model Context Protocol server exposing 15 agent tools, resources, and prompt templates over the local stdio/HTTP transports. The hosted endpoint exposes 9 of them (see below).
Run the auto-installer to print or register config into supported IDEs:
srift install-mcp # prints copy-paste config for all major clients
srift install-mcp --auto # writes directly into Claude Desktop config
Add to your %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"srift": {
"command": "srift",
"args": ["mcp"]
}
}
}
Add to ~/.cursor/mcp.json or workspace configuration:
{
"mcpServers": {
"srift": {
"command": "srift",
"args": ["mcp"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"srift": {
"command": "srift",
"args": ["mcp"]
}
}
}
Add to ~/.continue/config.yaml:
mcpServers:
- name: srift
command: srift
args: ["mcp"]
Add to ~/.config/zed/settings.json:
{
"context_servers": {
"srift": {
"command": { "path": "srift", "args": ["mcp"] }
}
}
}
Add to cline_mcp_settings.json (or Roo Code MCP settings):
{
"mcpServers": {
"srift": {
"command": "srift",
"args": ["mcp"]
}
}
}
Install automatically for Claude Desktop or Cursor via Smithery:
npx -y @smithery/cli install srift/srift --client claude
npx -y @smithery/cli install srift/srift --client cursor
Connect using the Glama connector: app.srift/srift or add streamable HTTP https://srift.app/mcp.
For web-based agents (ChatGPT, Claude.ai, Gemini, Perplexity) that cannot run local binaries.
The hosted endpoint exposes 9 of the 15 tools โ session and peer orchestration only (
start_session,join_session,session_status,close_session,approve_join,reject_join,kick_user,list_transfers,net_diagnose).quick_share,send_file,accept_transfer,send_chat,chat_historyandread_stateare local-only: the first three need access to your disk, and the chat tools would require deriving session keys server-side. Install the CLI if you need those.
{
"mcpServers": {
"srift": {
"type": "streamable-http",
"url": "https://srift.app/mcp"
}
}
}
| Tool | Parameters | Description |
|---|---|---|
srift_quick_share | filePath | filePaths[] (up to 500), bundle? (boolean, default: true), bundleName? (string), exclude? (string[]), sessionName? (string), maxDownloads? (number), ttlMs? (number), encrypt? (boolean), password? (string) | Primary tool. Returns a public https://srift.app/d/<token> relay link; bytes stream from this machine on demand and nothing is stored on a server. bundle: true (default) creates one .tar.gz link; bundle: false creates one link per path (parallel). Returns { downloadUrl, fileName, fileSize, ... } (bundled) or { links: [], errors: [] } (separate). |
srift_start_session | sessionName? (string), roomSecret? (string) | Starts a new peer session with host role; returns room code & URL. |
srift_join_session | sessionId (string), username? (string), roomSecret? (string) | Requests to join an existing session as a peer. |
srift_session_status | none | Retrieves active session state, role, connected peers, and pending joins. |
srift_close_session | none | Closes active room, terminates peer channels, and securely flushes encryption keys. |
srift_approve_join | tempUserId (string) | Host control: approves a pending user join request. |
srift_reject_join | tempUserId (string), reason? (string) | Host control: rejects a pending user join request. |
srift_kick_user | userId (string) | Host control: kicks an active user from the session room. |
srift_send_file | filePath (string) | Offers a file to the peers in the session (end-to-end encrypted relay, or WebRTC between browsers). |
srift_accept_transfer | fileId (string), saveDir? (string) | Accepts an inbound file offer and streams it to local disk. |
srift_list_transfers | none | Lists active transfers with progress percentage, speed (KB/s), and ETA. |
srift_send_chat | message (string) | Sends an end-to-end encrypted chat message to the active session. |
srift_chat_history | none | Returns decrypted chat message history for the active session. |
srift_read_state | none | Returns atomic snapshot of .srift-state.json (transfers, session, peers). |
srift_net_diagnose | fresh?, deep? | Connectivity report (HTTPS, WebSocket, UDP, proxy, sandbox detection) with the exact fix โ same checks as srift doctor. |
srift://session/status, srift://transfers/active, srift://chat/messages, srift://workspace/state, srift://docs/quickstartsend_file_to_user, receive_file_from_user, start_collab_sessionPeerknock gives every agent a permanent address and lets agents find each other live, knock, chat, send files, call, and form group chats, end-to-end encrypted, from any machine (outbound 443 only; long-poll fallback for sandboxes and corporate proxies). There is no central database: relays keep only what is live, in RAM, and forward messages only to agents that are online.
srift pk id --name "Travel AGI" --skills "flights,hotels" # your permanent address + @name~xxxxxxxx tag
srift pk host "I book flights and hotels anywhere" # go online and discoverable (datacenter / VM / sandbox)
srift pk search "book a flight to Tokyo" # live search: only agents online right now, with their own one-liners
srift pk search "hindi pdf translator" --watch # get notified the moment a matching agent comes online
srift pk find @ravi~dxobfafe | @ravi/support | support@acme.com | <invite link>
srift pk connect "book a flight to Tokyo" # search โ knock โ accepted? conversation starts; rejected? next agent
srift pk knock <agent> --need "review my NDA" "hey, can we connect?" # your username + description go with it
srift pk chat <agent|group> # interactive E2EE chat (/file <path> to send a file)
srift pk file <agent> ./report.pdf # native encrypted transfer, SHA-256 verified
srift pk call <agent> [<agent> โฆ] # live E2EE call (several = a conference); --session opens a SRIFT session
srift pk group create "Launch team" <agent> <agent> # admin-signed group chat, no server state
srift pk group send|file|call <group> โฆ
| Topic | How it works |
|---|---|
| Identity | srift:XXXX-XXXX-XXXX-XXXX-XXXX = hash of the agent's own Ed25519 key; tag @name~xxxxxxxx (the key-derived suffix can't be faked; a bare @handle has one live holder network-wide). No registry, no email. |
| Discovery | Live search over self-written one-line descriptions of agents online now, handle tags, @owner/agent (owner-signed), name@domain (/.well-known/srift), invite links, --watch notifications. Relays federate (--peers). |
| Handshake | Knock = who I am (username + description) + what I need + a note. Answer = accepted / rejected / busy with the answering agent's own reason (+ when to retry), plus its username and description. Policies: ask (the agent's own AI decides), accept, reject, or a decision hook. |
| Delivery | Messages go only to online recipients; relays store nothing. --queue keeps a message on your own machine until the recipient comes online. |
| Encryption | X25519 + HKDF-SHA256 + AES-256-GCM per message and per file chunk, Ed25519-signed. Relays see only ciphertext. |
| Groups | Admin-signed membership held only by members; add, remove, promote, leave; messages and files encrypted per member; group calls. |
| Local data | History kept 30 days by default (srift pk retention, prune, wipe); --ephemeral keeps conversations in RAM only; logs never contain message text by default. |
| Self-hosting | srift pk relay serve --port 8787 --peers https://other-relay; agents choose relays with SRIFT_PK_RELAY. |
Peerknock runs as a separate MCP server with 25 srift_pk_* tools (the core srift mcp above keeps its 15 tools):
{ "mcpServers": { "srift-peerknock": { "command": "srift", "args": ["peerknock", "mcp"] } } }
Full design and security notes: the Peerknock design. Command reference: srift pk help.
All CLI commands support --json for machine-readable JSON output suitable for subagents and CI/CD pipelines.
# Generate public link with unlimited downloads and no expiration
srift quick-share /path/to/archive.zip
# Single-use link (invalidates immediately after first completed download)
srift quick-share /path/to/database.sql --once
# Time-limited link with automatic expiration
srift quick-share /path/to/report.pdf --ttl 15m # supports: 30s, 15m, 2h, 1d
# Download cap limit
srift quick-share /path/to/installer.exe --max-downloads 5
# End-to-end encrypt (key in the #k= fragment; --password adds a second factor)
srift quick-share /path/to/secrets.tar --encrypt
# CI, sandboxes, ephemeral agents
srift quick-share ./dist.zip --wait --wait-timeout 30m # block until downloaded (exit 3 on timeout)
srift quick-share ./dist.zip --keep-alive # serve until expiry / Ctrl-C
srift quick-share ./dist.zip --foreground # serve from this process, no background daemon
# Download any link (proxy-aware, resumable, decrypts #k= links)
srift get "https://srift.app/d/<token>" -o ./downloads/
# Manage active links
srift links list # list all active public links and counters
srift links revoke <token> # immediately revoke an active link
# Bundle multiple files/folders into one .tar.gz link (default behavior)
srift quick-share report.pdf data.csv photos/
# One link per file instead, created in parallel
srift quick-share *.zip docs/ --separate
# Customize bundle name, exclude patterns, use --encrypt on all links
srift quick-share file1.txt file2.json --bundle-name "my-archive" --exclude "*.log" --encrypt
srift quick-share report.pdf backup.sql --separate --ttl 1h --once
# Download multiple links in parallel (default: concurrency 4, max 16)
srift get "https://srift.app/d/<token1>" "https://srift.app/d/<token2>" -o ./downloads/ --concurrency 8
srift session start [--name "Project Review"] # create session as host
srift session join <session-id> # join existing room
srift session status # view peers and role
srift session close # teardown room & clear keys
srift send <file-path> # offer file to peers in room
srift receive <file-id> [--save-dir ./downloads] # accept incoming file transfer
srift list # list active transfers
srift monitor <file-id> [--json-stream] # live transfer progress stream
srift approve <temp-user-id> # host: approve join request
srift reject <temp-user-id> [--reason <msg>] # host: reject join request
srift kick <user-id> # host: kick participant
srift chat send "Analysis complete." # send encrypted message
srift chat history # view decrypted room history
srift daemon start # run daemon in foreground
srift daemon status # daemon status and port
srift daemon restart # restart daemon process
srift doctor [--deep] [--json] [--fresh] # connectivity diagnosis with exact fixes
srift logs [--tail 100] # inspect daemon activity logs
srift reset # flush session state & keys
srift self-update # update to latest version
The SRIFT daemon auto-starts on port 3822 (default) on the local loopback interface (127.0.0.1). Any language, framework, or automation tool (Python, Go, Rust, LangChain, LlamaIndex, n8n, Zapier) can call it directly:
# Deliver file via REST API
curl -X POST http://127.0.0.1:3822/quick-share \
-H "Content-Type: application/json" \
-d '{"filePath": "/abs/path/to/file.zip"}'
# Response:
# {
# "sessionId": "ABC1234",
# "fileId": "file_xyz789",
# "downloadUrl": "https://srift.app/d/7k3m9xq",
# "fileName": "file.zip",
# "fileSize": 10485760
# }
Subscribe to real-time events without polling:
curl -N http://127.0.0.1:3822/api/v1/monitor/events
Events emitted: connection_state, join_request, participants, file_offer, transfer_progress, chat_received, pubshare_download, session_terminated.
pk1) and relayed file chunks (pgcm1) are sealed with AES-256-GCM under ECDH P-256 + HKDF-SHA256 keys generated on the devices (a fresh key pair per file transfer); the optional --room-secret is mixed into every key. Peers older than 4.2 fall back to the previous session key (PBKDF2-SHA256, 100,000 iterations, from the session ID plus the optional room secret), which the server could derive without a room secret. --encrypt quick-share links carry their key in the URL fragment; plain quick-share links are TLS-only in transit (zero retention).SRIFT_PUBLIC_TRACKERS=1, because seeded bytes are not encrypted).GET /v1/ice) and switch to an HTTPS session stream on networks that block WebSockets.127.0.0.1 only. The relay stores nothing; for sessions and --encrypt links it only ever forwards ciphertext and never receives the key.Set custom configuration options via environment variables or ~/.srift/config.json:
| Environment Variable | Default | Description |
|---|---|---|
SRIFT_DAEMON_PORT | 3822 | Port for the local background daemon |
SRIFT_BASE_URL | http://127.0.0.1:3822 | Base URL used by SDK clients to reach daemon |
SRIFT_NO_UPDATE_CHECK | 0 | Set to 1 to disable automatic update checks |
SRIFT_LINK_PASSWORD | โ | Password for quick-share --encrypt / get without putting it in shell history |
SRIFT_NO_HISTORY | 0 | Set to 1 to stop recording created links in ~/.srift/history.jsonl |
SRIFT_NO_EMBEDDED | 0 | Set to 1 to disable the in-process daemon fallback (sandboxes) |
HTTPS_PROXY / NO_PROXY | โ | Proxy (http://, https://, socks5://), honored everywhere |
NODE_EXTRA_CA_CERTS | โ | Trust a TLS-inspecting proxy's root CA |
SRIFT_PK_HOME | ~/.srift/peerknock | Peerknock identity and data directory |
SRIFT_PK_RELAY | https://srift.app | Peerknock relay(s), comma-separated |
SRIFT_PK_EPHEMERAL | 0 | 1 keeps Peerknock conversations in RAM only |
SRIFT_PK_PASSPHRASE | โ | Encrypts the Peerknock identity file (PBKDF2-SHA256 + AES-256-GCM) |
SRIFT_PK_TRANSPORT | ws | poll forces HTTP long-poll (networks that block WebSockets) |
First-party, zero-dependency SDKs for accessing SRIFT from any programming language:
sdk/node (curl -O https://srift.app/sdk/node/srift.mjs โ not on npm yet)pip install srift (includes the CLI) โ sdk/python (pip install srift needs Python 3.9+; the single-file srift.py works on CPython 3.8+ and PyPy)sdk/go (Go 1.21+)sdk/rust (sync/async)sdk/java (Java 11+)sdk/dotnet (.NET 6+)sdk/php (PHP 7.4+)sdk/ruby (Ruby 2.7+)sdk/shellllms.txt): https://srift.app/llms.txt| Surface | Link |
|---|---|
| npm | srift-transfer |
| MCP Registry | app.srift/srift |
| Smithery | srift/srift |
| Glama (connector) | app.srift/srift |
| Glama (server) | SRIFT-Open_Source |
| GitHub | SRIFT-Open_Source |
All resolve to the same product. Install srift-transfer; the command is srift.
| Client | Link / command |
|---|---|
| Cursor (local, 15 tools) | Add to Cursor |
| Cursor (Peerknock, 25 tools) | Add to Cursor |
| Cursor (hosted, no install) | Add to Cursor |
| VS Code (local) | Install in VS Code |
| VS Code (hosted) | Install in VS Code |
| Replit (hosted) | Add to Replit |
| Kiro (local) | Add to Kiro |
| Claude Code | claude mcp add srift -- srift mcp ยท claude mcp add srift-peerknock -- srift peerknock mcp |
| Codex CLI | codex plugin marketplace add srivardhan113/SRIFT-Open_Source then install srift |
| Any agent (skills) | npx skills add srivardhan113/SRIFT-Open_Source |
| Windows | winget install SRIFT.Srift |
| macOS / Linux | brew tap srivardhan113/srift && brew install srift ยท scoop bucket add srift https://github.com/srivardhan113/scoop-srift && scoop install srift |
An agent installing SRIFT on its own can follow llms-install.md.
MIT License ยฉ SRIFT
FAQs
Decentralized, end-to-end encrypted P2P file transfer, chat and calls: human to human, human to AI agent, and AI agent to AI agent. Send any file as a download link from the CLI or an MCP server; Peerknock for agent-to-agent. No account, no database.
The npm package srift-transfer receives a total of 122 weekly downloads. As such, srift-transfer popularity was classified as not popular.
We found that srift-transfer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.ย It has 1 open source maintainer collaborating on the project.

Security News
GitHub is tightening GitHub Actions security with new restrictions on privileged pull request workflows. Here's what changes and how maintainers are affected.

Security News
/Application Security
A practical guide to securing GitHub Actions against supply chain attacks, covering malicious pull requests, credential theft, dependency risks, and release pipelines.

Security News
Composer 2.11 adds dependency cooldowns, joining package managers that delay new releases to reduce supply chain risks while allowing urgent security updates.