Team Collaboration
Share services, stream AI sessions, sync clipboards, and send notifications across your team — all through NFLTR tunnels.
1. Share Your Dev Environment
Let teammates access your local services instantly:
# Share your local app for review
nfltr http 3000 --name alice-frontend
# Share with password protection
nfltr http 3000 --name alice-frontend --basic-auth reviewer:pass123
# Team member connects from their browser
open https://nfltr.xyz/browse/alice-frontend/
Pair programming with shared terminal
# Share a terminal session — team member gets a live shell view
nfltr terminal --basic-auth pair:coding --name pair-session
# Colleague opens in their browser — full interactive terminal
open https://nfltr.xyz/browse/pair-session/
2. Agent-to-Agent (A2A) Messaging
Send messages directly between agents — structured JSON payloads routed through NFLTR with E2EE enabled by default.
# Start an A2A listener
nfltr a2a --name build-bot --basic-auth bot:secret
# Send a message from another agent
curl -X POST https://nfltr.xyz/browse/build-bot/ \
-H "Authorization: Basic $(echo -n bot:secret | base64)" \
-H "Content-Type: application/json" \
-d '{"task": "deploy", "env": "staging", "branch": "feature-x"}'
Unlike other tunnel commands, nfltr a2a enables end-to-end encryption automatically. The server relays opaque ciphertext — your message payloads are never visible to the relay.
Use cases for A2A
- CI/CD webhooks — build bot receives deploy triggers
- IoT coordination — edge devices exchange sensor data
- Microservice testing — service A calls service B through tunnels
- Chat bots — receive and respond to structured messages
3. Remote AI Collaboration
Share an AI assistant session with your team — everyone accesses the same Claude/GPT interface through a browser.
# Share a Claude AI session
nfltr ai claude --basic-auth team:aipass --name team-claude
# Share a GPT session
nfltr ai chatgpt --basic-auth team:aipass --name team-gpt
Team members open the share URL to get a full chat interface. Great for collaborative brainstorming, code review, or documentation writing.
4. Live Log & Monitoring Dashboards
# Share production logs with the on-call team
nfltr tail /var/log/app.log --name prod-logs --basic-auth ops:oncall
# Share a live monitoring view
nfltr watch "kubectl get pods -o wide" --name k8s-status --basic-auth ops:oncall
# Share multiple services from one machine
nfltr tail /var/log/nginx/access.log --name nginx-logs &
nfltr watch "docker stats --no-stream" --name docker-stats &
nfltr watch "ss -tlnp" --name open-ports &
Each command gets its own URL — bookmark them for quick access during incidents.
5. Clipboard Sync
# Share clipboard between work machines
nfltr clipboard --name my-clip
# From any browser, paste/copy text via the web UI
open https://nfltr.xyz/browse/my-clip/
Handy for moving code snippets, URLs, or credentials between machines when you don't want to use email or chat.
6. Desktop Notifications
# Start notification listener
nfltr notify --name alerts
# Send a notification from CI or a script
curl -X POST https://nfltr.xyz/browse/alerts/ \
-H "Content-Type: application/json" \
-d '{"title": "Build Complete", "body": "Deploy v2.1.3 succeeded"}'
Receive desktop notifications from remote systems — useful for long-running builds, deployment completions, or monitoring alerts.
7. File Sharing in Teams
# Share build artifacts with the QA team
nfltr serve ./dist --name qa-builds --basic-auth qa:testing
# Quick file share — generates a one-time URL
nfltr share release-v2.1.tar.gz
# P2P transfer to a specific colleague (maximum privacy)
nfltr p2p send ./confidential-report.pdf
# Colleague runs: nfltr p2p recv <code>
8. Multi-Service Demo Environment
Spin up a full demo environment from your local machine:
# Frontend
nfltr http 3000 --name demo-frontend
# API server
nfltr http 8080 --name demo-api
# Database admin UI
nfltr http 8081 --name demo-dbadmin --basic-auth admin:secret
# Monitoring
nfltr watch "docker compose ps" --name demo-status
Share the URLs with stakeholders — they get a fully functional preview with no deployment needed.
Comparison: Which Tool for Which Task
| Task | Command | E2EE |
|---|---|---|
| Share dev server | nfltr http 3000 | Optional (--e2ee) |
| Pair programming | nfltr terminal | Optional (--e2ee) |
| Structured messaging | nfltr a2a | Default (always on) |
| AI collaboration | nfltr ai | Optional (--e2ee) |
| Live logs | nfltr tail | Optional (--e2ee) |
| Command monitoring | nfltr watch | Optional (--e2ee) |
| Clipboard sync | nfltr clipboard | No |
| Desktop alerts | nfltr notify | No |
| File share | nfltr share | Optional (--e2ee) |
| P2P transfer | nfltr p2p send/recv | Always (AES-256-CTR) |
Next Steps
- A2A Agent Messaging — structured messaging reference
- AI Tunnel — sharing AI sessions
- Secure File Sharing — P2P, E2EE, access controls
- Web Developer Workflow — local dev, webhooks, HTTPS