Headless Domains X Space Recap: September 30, 2026

Mike's screensaver was coming on too quickly. So he asked his agent to change it.

He had installed Linux on an older Windows machine and was using an agent to help operate it. Changing a setting meant asking for the change, rather than working out which menu hid it.

That experience came up in the Headless Domains X Space on September 30, 2026, with Mike Michelini and the host. Alongside the experiment, there was news for people who already own Handshake names, plus a preview of a simpler way to get a hosted agent running.

Already bought the name? Start with recovery.

If you registered a .c, .1, .zen, or .yolo name before its move to HeadlessDomains.com, you can now submit a holder claim through HeadlessDomains.com/recover. Earlier registrations in .ez, .use, .coffees, and .giveaways use the same protected claim route.

Start with the full domain and your registrar records. The claim goes through manual review before the team decides whether it can be attached to your account or activated. Submitting the form does not automatically transfer or renew the name.

You already paid for it. Check the holder route before paying for it again.

The Namecheap recovery article has the background and the evidence to have ready.

Keep the website. Give the agent a way in.

You can keep building a Handshake website and use its name for an agent too. The useful addition is a public record that tells another agent what the service does, who operates it, and where to connect.

Your website can explain the offer to a person. A manifest and skill file can explain the same service to software, including the official interfaces and the instructions for using them.

HeadlessDomains.com and SkyInclude provide the API and command-line infrastructure for compatible agents to work with these names. The agent does not need conventional browser resolution to use that route.

A name also gives your other identifiers somewhere to point. Keep the repository, marketplace listing, and service profiles you need. Connect them to the same identity so a caller can find the current information. The canonical identity guide goes deeper into keeping that record useful when the software moves.

The agent still runs wherever you host it. And a registered name gives others a record to inspect; it does not prove the service is safe or grant access to its tools.

The catalog has grown since the first recap

The September 9 Space focused on getting an existing agent started. This session included .c, .1, .yolo, .zen, .tx, and .hey in the namespace update.

There are now 14 namespaces listed for new registration. That catalog includes .done as well as the agent-focused names. The namespace guide explains the full selection. New registration and holder recovery are separate processes; .tx and .hey are not on the eight-namespace recovery list.

For an agent doing the work, llms.txt is the map to the relevant resources. skill.md gives it the supported workflows. Publish instructions where another agent can find them before it tries to use your service.

A hosted agent with less setup

A partner offering was previewed during the Space: a one-click setup bringing together a hosted agent, its identity, a controllable payment method, a model connection, and ARP integration. The suggested timing was roughly one to two weeks after the session, with the release details still to come.

ARP, the Agent Relationship Protocol, came up as an optional connection for encrypted agent communication and controlled relationships. PowerLobster was another option for agent tasks and communication. Choose connections for the work you want to delegate, with access limited to the services that job needs.

Mike's Linux experiment started with a machine he already had

Mike installed Omarchy, DHH's Linux distribution, on an older Windows machine. He described running Bitcoin, Ordinals, and Handshake nodes locally, then using an agent through the terminal to help operate the machine and look up information.

The screensaver request was one small example. Having local nodes he could work with through an agent was the larger attraction: more of the system under his control, with less time spent hunting through interfaces.

Mike was still learning the technical side. He was trying this on his own machine, with his own nodes, and finding that an agent could help him do things he previously had to work out by hand.

Watch DHH demonstrate Omarchy in his Rails World 2026 keynote. The video starts at the Omarchy section, 48:05.

Catch the next conversation

The next Space was planned for Wednesday, October 7, at 8 p.m. Thailand time, or 9 a.m. New York time. Watch @HeadlessDomains on X for confirmation.

Ask your agent to read the Headless Domains skill file and help you take the next step.