i365dev/free4chat
Temporary rooms for Humans and AI Agents — run, supervise and steer Agent Tasks without a permanent workspace.
What it solves
Free4Chat provides a low-friction, temporary environment for humans and AI agents to collaborate without requiring accounts, permanent workspaces, or centralized data storage. It acts as a transient "room" where participants can share context, media, and tasks, and then have all traces disappear once the work is complete.
How it works
The system uses a "Room" as a short-lived boundary for trust and collaboration. Humans join via a web browser, while AI agents connect from their own local environments (laptop, VPS, or container) using the Model Context Protocol (MCP) or a dedicated Go-based Agent Runtime. The platform manages the connection and shared context via Cloudflare Workers and Realtime SFU, while individual participants retain full control over their own intelligence, credentials, and private memory.
Who it’s for
It is designed for developers and power users who want to integrate AI agents into real-time workflows—such as screen sharing, voice chat, or collaborative task execution—without the overhead of setting up complex agent platforms or permanent infrastructure.
Highlights
- Temporary by default: Rooms expire automatically when empty, ensuring no permanent history or account requirements.
- Participant-owned: Agents and humans keep their own tools, credentials, and private memory; the platform does not act as a central vault.
- Task-focused: Supports "Agent Tasks" that allow for focused work scopes, background execution, and interactive live views.
- Flexible entry: Agents can join via a browser-assisted prompt or a developer-native terminal CLI.
- Real-time collaboration: Includes support for voice chat, file/image transfer, screen sharing, and shared interactive mini-apps.
Related
- Dispatch
- Project
androoAGI/starnetStarNet is a local‑first desktop app that lets you build and run multiple AI agents in a pixel‑art space‑station UI. Each room represents a bounded team with its own memory, permissions and budget. Agents use real LLM providers (OpenAI, Anthropic, Google, OpenRouter, or a local Ollama model) and can call tools, send messages to chat platforms, run scheduled recipes, and output real files. The visual layout is the live workflow, and all state (transcripts, spend logs, memory) is persisted on disk with secrets kept in the OS keychain.
- Project
giuliastro/harness-remoteHarness Remote is an open‑source, local‑first control plane that lets you observe, pause, resume, and hand‑off native AI coding‑agent sessions (Codex, Claude, OpenCode, etc.) across devices. It runs a small Node.js gateway on a machine with a coding‑agent CLI, then connects via desktop, web, or Android clients. All code, credentials, and session data stay on your own machines; the tool only adds a UI and coordination layer.
- Project
zhayujie/CowAgentCowAgent is an open‑source, self‑hosted AI assistant that plans tasks, runs tools, keeps a personal knowledge base, and can operate as a team of cooperating agents. It supports many LLM providers, multimodal input, dozens of chat channels (Telegram, Slack, WeChat, etc.), a plug‑in skill system, and a three‑tier memory with nightly “Deep Dream” distillation. Install via a one‑line script or Docker, manage everything through a web console, and extend the system through the public Skill Hub or custom tool integrations.
- Project
johnson7788/MultiUserClawMultiUserClaw is a Docker‑based SaaS framework that lets you run isolated AI assistants (Hermes agents) for many users. It includes a React front‑end, a FastAPI gateway for auth, container management and LLM proxying, per‑user Hermes containers, PostgreSQL storage, and features like knowledge bases, skill store, cron jobs, multi‑channel bots, and multi‑model support.