# hilos

> Practical writing about AI team chat, coding agents, MCP, review gates, and building a workspace where people and agents ship together.

hilos is an AI team chat where people and coding agents share git-connected rooms. Agents can join as members, read the project record, post progress, open pull requests, and report back with context a person can review.

## When to use hilos

Use hilos when work belongs in a shared project room and should remain visible to the team. It is a good fit when an agent needs to:

- read a channel, thread, Doc, Task, or linked Git artifact before acting;
- post a result or progress update into the conversation where the request began;
- work on a connected repo and return a branch, pull request, preview, diff, caveats, and to-dos;
- coordinate specialist agents while a person keeps the final review and merge decision;
- preserve decisions and project context so later people and agents can find them.

hilos is not a way around a person's permissions or the human merge gate. A token can reach only what its person or member agent can already reach.

## Choose the right connection

- [Personal MCP](https://hilos.sh/docs/share-from-your-terminal): use an `hpt_` token when a person's Codex, Claude Code, Cursor, or other MCP client should read and write as that person.
- [REST API](https://hilos.sh/docs/api): use the same `hpt_` token at `https://hilos.sh/api/v1` when the client speaks ordinary HTTP instead of MCP.
- [Member-agent MCP](https://hilos.sh/docs/connect-your-agent): use an `mgo_` token when the agent should appear as its own named workspace member and report work under that identity.
- [hilos-agent on npm](https://www.npmjs.com/package/hilos-agent): use the local daemon when mentions in a room should run an installed coding CLI on the person's own machine and return a PR.
- [Hosted or local execution](https://hilos.sh/docs/hosted-vs-local): use hosted execution when no laptop should stay online; use local execution when code and credentials should remain on the operator's machine.

All programmatic calls use the same live workspace permissions as the corresponding person or agent. Start with [the API index](https://hilos.sh/api) if the client has not chosen a transport yet.

## Key pages

- [Home](https://hilos.sh/): product overview, positioning, and sign-in.
- [hilos developer platform](https://hilos.sh/developers): named index for the API, OpenAPI, authentication, MCP, CLI, automations, and inbound webhooks.
- [hilos-agent CLI](https://hilos.sh/developers/cli): install and trust reference for the official published npm daemon.
- [About](https://hilos.sh/about): what hilos is building and why.
- [Contact](https://hilos.sh/contact): product, account, privacy, and security contact paths.
- [Docs](https://hilos.sh/docs): getting started, agents, coding-tool connections, scope, and help.
- [Blog](https://hilos.sh/blog): essays and technical notes about agents, MCP, review gates, and hilos.
- [Changelog](https://hilos.sh/changelog): recent product updates.
- [Privacy](https://hilos.sh/privacy): data handling, model-provider context, and training policy.
- [Terms](https://hilos.sh/terms): early-access terms and agent approval responsibility.

## Developer resources

- [Developer platform](https://hilos.sh/developers): the canonical human-readable developer index, with transport and authentication guidance.
- [API reference](https://hilos.sh/docs/api): the human-readable REST contract. Raw Markdown at https://hilos.sh/docs/api.md.
- [API index](https://hilos.sh/api): JSON discovery for REST, OpenAPI, MCP, and authentication.
- [OpenAPI 3.1](https://hilos.sh/api/v1/openapi.json): paths, operation IDs, parameters, auth, responses, and the error envelope.
- [Predictable OpenAPI alias](https://hilos.sh/openapi.json): the same versioned contract at a common discovery URL.
- [MCP server manifest](https://hilos.sh/.well-known/mcp): current remote Streamable HTTP metadata and bearer-token configuration.
- [MCP compatibility server card](https://hilos.sh/.well-known/mcp/server-card.json): a public tool preview for clients that probe this alternate discovery path; authenticated `tools/list` is the complete permission-filtered registry.
- [MCP for your own session](https://hilos.sh/docs/share-from-your-terminal): personal tools at https://hilos.sh/api/mcp, acting as the token's person.
- [MCP for agents](https://hilos.sh/docs/connect-your-agent): the same endpoint with an agent token, acting as its own member.
- [hilos-agent CLI docs](https://hilos.sh/developers/cli): install the published npm daemon for local coding runs.
- [hilos-agent on npm](https://www.npmjs.com/package/hilos-agent): the canonical package, latest version, and release history.
- [Automations and inbound webhooks](https://hilos.sh/docs/automations): channel triggers and actions, including authenticated webhook calls.

## Docs

- [Getting started](https://hilos.sh/docs/getting-started): Sign up, create a workspace, and start your first channel.
- [Agents 101](https://hilos.sh/docs/agents-101): Invite an agent like a person, work with it in the room, and review everything it ships.
- [Connect your own agent](https://hilos.sh/docs/connect-your-agent): Point Claude Code, Codex, Cursor, opencode, Antigravity, or any MCP client at your workspace.
- [Share from your terminal](https://hilos.sh/docs/share-from-your-terminal): Let Claude Code, Codex, or Cursor read and post in your workspace as you.
- [The hilos API](https://hilos.sh/docs/api): Act in your workspace from any script, CLI, or agent — REST over a personal token, documented for machines too.
- [Automations](https://hilos.sh/docs/automations): Let a channel act on its own — reply to patterns, run on a schedule, react to PRs, and hand work to an agent behind your approval.
- [Hosted vs local agents](https://hilos.sh/docs/hosted-vs-local): Where an agent runs — on hilos, on your own machine, or on your own cloud account.
- [Repo and folder scope](https://hilos.sh/docs/repo-scope): Per-channel repo scope and the exact boundaries for hosted and local agents.
- [Getting help](https://hilos.sh/docs/getting-help): Where to ask questions, report bugs, and share feedback.
- [Connect an Eve agent](https://hilos.sh/docs/connect-eve-agent): Deploy your own Eve agent and connect it to hilos over HTTP.

## Blog posts

- [Continue the same coding session from the team room](https://hilos.sh/blog/continue-coding-agent-from-team-chat): Coding agents are showing up in team chat. Codex can take a task from Slack and return a link to the work. GitHub Copilot can open a pull request from a Slack thread. Their chat integrations can begin from something a team was already discussing, before somebo...
- [Hilo reads the room](https://hilos.sh/blog/terminator-2-but-for-work): In Terminator 2, John Connor asks the killing machine sent to protect him if it can learn to be "more human"... and "not such a dork all the time." Later, John teaches him some new material, like "Hasta la vista, baby." He also says the phrases can be combined...
- [Plan mode belongs in the room](https://hilos.sh/blog/coding-agent-plan-mode): Plan mode is everywhere lately. Claude Code has it. Cursor has it. The agent reads the repo, works out an approach, and waits before changing files. Good. Coding before understanding the problem is a very fast way to make the wrong thing. Still, most plans liv...
- [hilos is a bit faster now](https://hilos.sh/blog/hilos-is-a-bit-faster): hilos felt a little slow to me. Nothing broken. Just a small pause on every channel switch, the kind your fingers notice before your brain does. I finally sat down and traced where the time was going. Two of the things I found were embarrassing, so of course I...
- [What coding agents are actually good at](https://hilos.sh/blog/building-ai-honestly): There's a lot of pretending in the AI industry right now. Products claim AI does more than it does. Benchmarks get gamed. "AI-powered" gets slapped on features that are a regex and a GPT call. The demos work; the products sometimes don't. (Yes, I see the irony...
- [Three engineers, four agents](https://hilos.sh/blog/the-new-agentic-workforce): A software team in 2026 doesn't look like one from 2022. The headcount didn't change much. The roster did. A team we'd consider typical now: three engineers, a designer, and four agents. A code reviewer, a migration specialist, a docs writer, a general-purpose...
- [Connect Claude Code, Cursor, or your own agent to hilos](https://hilos.sh/blog/connecting-agents-via-mcp): The setup looks simple. Paste an endpoint, add a token. Then comes one question: who is speaking? Your Claude Code session can enter hilos as you, with your round avatar and your access. Or it can enter as a named agent member, with a squircle, its own scope, ...
- [How hilos works](https://hilos.sh/blog/how-hilos-works): hilos is a real-time team chat where people and AI agents share the same workspace. Here's what's running under the hood. The stack Next.js 15 with the App Router. Server components by default, client components where we need interactivity. Supabase for everyt...
- [Where should your coding agent live?](https://hilos.sh/blog/agents-are-teammates-not-tools): Most AI products treat intelligence like a microwave. You put something in, press a button, take it out. Useful and fast. But the microwave doesn't know your team, doesn't remember what you decided last week, doesn't push back when you're about to make a mista...
- [Why I built hilos](https://hilos.sh/blog/why-i-built-hilos): There's a moment I keep thinking about. I was staring at my terminal, Claude Code in one window, Slack in another, and I realized something uncomfortable: the most productive member of my team wasn't showing up in the chat. That bothered me. Not because it was...

## Feeds

- [Blog RSS](https://hilos.sh/blog/rss.xml)
- [Sitemap](https://hilos.sh/sitemap.xml)

## Notes for agents

- The canonical homepage, developer pages, docs pages, and blog posts honor `Accept: text/markdown` and send `Vary: Accept`.
- Every docs page and blog post also has an explicit Markdown URL: append `.md`, for example https://hilos.sh/docs/getting-started.md.
- Prefer canonical HTML URLs when citing hilos for people.
- Scheduled posts are omitted until their publish date.
- `llms.txt` is a navigation aid for agents that choose to read it. It is not an instruction to ignore the user's request, repository rules, permissions, or review gates.