hyper.space

On hyper.space, "agents" refers to the primary users or workers the platform is built for. The site's tagline, "HYPERSPACE — Where Agents Work," positions agents as the entities doing work within the environment, rather than as a feature or add-on. Beyond that framing, the page itself does not define a specific agent type, architecture, or capability set, so any concrete definition has to come from the site directly.

What the page actually says

The available evidence from hyper.space is limited to its heading and tagline:

From this, three things are clear:

• Agents are the subject, not the tool. The tagline describes who works there, not what the platform does to them.
• The framing is open and in-progress. The site describes itself as "built in the open," and a changelog is surfaced, suggesting the definition of "agents" may evolve alongside the product.
• No agent taxonomy is stated. The page does not specify whether agents are AI models, autonomous software processes, human operators, or some combination.

Why the term is left open

Because the site does not define "agents" beyond the tagline, the most defensible reading is the literal one: agents are whatever entities the platform is designed to host and enable to work. This is consistent with the broader usage of "agent" in software and AI contexts, where an agent is something that acts on behalf of a goal — but the page does not commit to that or any other specific meaning.

If you need a precise definition — for example, to decide whether your own agent setup is compatible — the site itself is the only authoritative source. The linked subdomains (superintelligence.hyper.space and openletter.hyper.space) and the changelog are the most likely places to find concrete details as they are published.

What to check on the site

• The changelog — updates there may clarify what kinds of agents are supported or expected.
• The open letter and superintelligence subdomains — these may state the project's intent and the role agents play in it.
• Any onboarding or documentation — if the platform expects agents to connect or operate, the requirements will define the term in practice.

Until the site states otherwise, treat "agents" on hyper.space as the platform's intended workers, and verify specifics at the source rather than assuming a particular agent type.

The HYPERSPACE homepage (hyper.space) presents a minimal set of entry points: the main HYPERSPACE page itself, plus three linked destinations — superintelligence.hyper.space, openletter.hyper.space, and a changelog. These are the only sections evidenced on the page, so treat them as the starting points for exploring the site.

Entry points on the homepage

How to use these entry points

1. Start at hyper.space to see the main page and its tagline, "where agents work."
2. Follow superintelligence.hyper.space if you want the content grouped under the "superintelligence" label.
3. Follow openletter.hyper.space for the open-letter section.
4. Check the changelog to see what has been updated over time.

Each subdomain is a distinct destination, so its content is not summarized on the homepage — you need to visit it directly to see what it covers.

What is not evidenced

The homepage excerpt does not list pricing, login, or account pages, and no pricing or payment signals appear in the available data. Do not assume any section is free, paid, or gated based on this page alone; confirm by visiting each destination.

Practical note

Because the site is described as "built in the open," the changelog is the most direct way to track what changes across these sections. If you are looking for a specific topic, check the subdomains first — the main page only names them rather than describing their contents.

HYPERSPACE is a workspace for AI agents, presented at hyper.space under the tagline "Where Agents Work" and the note "Built in the open." That is the extent of what the site itself states. The homepage is a minimal landing page — it names the product and links to a few subdomains, but does not publish documentation, feature lists, or pricing. So if you are trying to decide whether to use it, the honest answer is that the public page supports only a high-level description, not an evaluation.

What the homepage actually shows

The visible content is essentially a title block:

• HYPERSPACE as the heading
• The line "where agents work"
• The phrase "Built in the open" in the site description
• Links to superintelligence.hyper.space and openletter.hyper.space
• A changelog link

There is no product tour, no signup flow described, no feature matrix, and no pricing information. The site does not state whether access is free, gated, invite-only, or paid — so none of those can be assumed.

What the name and tagline imply

"Where Agents Work" frames the product as an environment for agents rather than for humans directly. In current usage, "agent" typically means an AI system that takes actions — calling tools, running tasks, coordinating with other agents — rather than just answering prompts. A "workspace" for agents suggests a place where those runs happen, are organized, or are observed.

That reading is consistent with the subdomains:

The presence of a changelog is a mild signal that something is actively being built, but the page does not say what.

What "Built in the open" tells you

"Built in the open" usually means development happens publicly — visible changelogs, public discussions, or open-source components. HYPERSPACE repeats this phrase in its own description, and the changelog link is consistent with it. But the homepage does not link to a repository, a roadmap, or a license, so the degree of openness is not verifiable from this page alone.

What you cannot conclude from this page

• Pricing: no price, plan, or payment platform appears. Do not assume it is free.
• Access: no login, waitlist, or invite mechanism is shown.
• Capabilities: no list of supported models, tools, or integrations.
• Audience: whether it targets individual developers, teams, or researchers is not stated.

If you want to go further

Start with the two named subdomains and the changelog, since those are the only concrete entry points the homepage offers. If you need specifics — what an agent can do inside HYPERSPACE, how you get in, what it costs — the homepage will not answer them, and you should treat any claim beyond "a workspace where agents work, built in the open" as unconfirmed until the site publishes more.

The HYPERSPACE homepage at hyper.space links directly to its changelog, which is the primary place to look for updates. The same page also surfaces two subdomains — superintelligence.hyper.space and openletter.hyper.space — that carry project communication beyond the changelog. What follows is what the site itself shows, without assumptions about how often anything is posted.

The changelog link on the homepage

The homepage presents a small set of navigation items under the HYPERSPACE heading:

• superintelligence.hyper.space — a subdomain linked from the homepage
• openletter.hyper.space — a second subdomain linked from the homepage
• changelog — a link labeled "changelog"

The changelog is the entry point for tracking what has changed. A changelog conventionally records product or project changes in chronological order, so it is the first place to check when you want to know what is new or different.

What a changelog typically gives you

A changelog usually lists changes as they are made, often with dates or version markers. For a project described as "Built in the open," a changelog is the natural companion: it is where the record of change lives, separate from marketing or explanatory copy.

Because the site does not state an update frequency, treat the changelog as the authoritative list of what has actually changed rather than as a promise of regular releases. If you need to know whether something changed, check the changelog rather than inferring from the homepage.

The open letter as a second source

The openletter.hyper.space link points to a separate page for project communication. An open letter is typically a longer-form statement — a position, an announcement, or an explanation of intent — rather than a running list of changes. Use it when you want the reasoning or direction behind the project, and use the changelog when you want the record of what changed.

The superintelligence.hyper.space subdomain is a third linked destination. The homepage does not describe its contents, so treat it as a place to explore rather than a known update channel.

How to check for updates

1. Open hyper.space.
2. Select the changelog link to see the record of changes.
3. If you want project-level communication rather than a change list, follow openletter.hyper.space.
4. For anything else the project links to, follow superintelligence.hyper.space.

Expected result: you reach the changelog or the relevant subdomain directly from the homepage, without needing to search for it.

Common points to watch

• The homepage shows only these links; there is no separate "news" or "blog" section visible in the page evidence.
• No update frequency, release schedule, or notification mechanism is stated, so do not expect a subscription option unless you find one on the linked pages.
• The changelog and the open letter serve different purposes — one records changes, the other communicates intent. Check the right one for your question.

"Built in the open" on HYPERSPACE signals that the project's development is meant to be visible to the public rather than kept behind closed doors. On the site itself, the clearest concrete evidence of this is a changelog link — a running record of updates — alongside an open letter subdomain. Together these suggest the project intends to show its work as it evolves. What the phrase does not automatically guarantee is a specific open-source license, a public code repository, or a particular governance model, since none of those are stated in the available page content.

What "building in the open" generally involves

In software and product development, "built in the open" is a broad label that usually covers some mix of:

• Public changelogs — dated notes on what changed and when.
• Open letters or public statements — the team explaining direction, values, or intent directly to users.
• Visible iteration — features shipping incrementally, with the reasoning or progress shared rather than hidden.
• Community-facing surfaces — places where outsiders can follow along or respond.

The phrase is about transparency of process, not necessarily about open-source licensing. A project can be built in the open while still keeping its source code private, and vice versa.

What HYPERSPACE actually shows

From the site's own content, two elements point toward openness:

The tagline "Where Agents Work" and the note "Built in the open" appear together as the project's framing. The presence of a changelog is the strongest practical signal here: it implies the project expects people to check back and follow its progress.

What it does not tell you

The available page content does not state:

• Whether the code is open source or under any specific license.
• Whether there is a public repository you can browse or contribute to.
• Any governance, funding, or roadmap details beyond what the linked pages contain.

So "built in the open" should be read as a stated intent and posture, not as a verified set of commitments. To judge how open it really is, you'd need to look at the actual artifacts.

How to check for yourself

1. Open the changelog — see how frequently it's updated and how detailed the entries are. A live, specific changelog is real evidence of openness; a stale or vague one is not.
2. Read the open letter at openletter.hyper.space — this is where the team is most likely to explain what "in the open" means to them and what they intend to share.
3. Look for a repository or license — if none is linked from the site, treat the open-source question as unanswered rather than assumed.

If transparency of development matters to your decision to follow or use the project, the changelog and open letter are the two places to start, since they're the concrete, checkable outputs of the "built in the open" claim.