Our Response to the Trademark Complaint Against Claude Remote

Today we received notice of a trademark complaint targeting clauderc.com and the Claude Remote project.

We take legal notices seriously. We are reviewing the complaint carefully, updating public messaging where appropriate, and responding through the proper channels. At the same time, we want to explain clearly why we disagree with the core premise behind this complaint.

This post is not legal advice. It is our public statement of record about the product, the name, and the role this project plays in the broader Claude developer ecosystem.

1. We do not believe the word "Claude" should be treated as untouchable across all software

Our disagreement starts with a basic point: Claude is not an invented nonsense word. It is a human name with a long history, and for many developers it is also associated with one of the greatest scientists in information theory, Claude Shannon.

Anthropic chose to use Claude as the name of its model family. That does not mean every use of the word in every software context should automatically be treated as illegitimate.

In our view, software naming should be judged in context:

• what the product actually does
• how it is branded
• whether it falsely claims affiliation
• whether it confuses users about source or sponsorship

Claude Remote has always been a companion product built for Claude Code users. It is not presented as Anthropic's official client, and it does not claim to be made by Anthropic.

We understand that Anthropic may want to protect its brand. That is reasonable. What we disagree with is the much broader implication that developers should be pushed out of using a common personal name in a clearly different product context.

2. We built this product before Anthropic shipped an official remote experience

Claude Remote did not appear to imitate an existing Anthropic remote product. We built it to solve a real workflow gap for Claude Code users.

When we launched the public open beta of Claude Remote, Anthropic had not released an official mobile remote-control workflow for Claude Code. There was no official iPhone companion app, no official approval-from-phone interface, and no official remote session management experience like the one we built.

That matters.

Claude Remote was not a clone of an existing official product. It was an independent developer tool built to extend the usefulness of Claude Code for people who were already paying Anthropic and already using Claude in their daily work.

We did the product design work, the systems work, the session lifecycle work, the mobile UX work, the notification work, and the security tradeoff work required to make that experience practical.

This is what healthy developer ecosystems usually look like: users of a platform build useful companion tools around the platform.

3. Claude Remote is a community product built by Claude users, for Claude users

Claude Remote is not a parasitic project built outside the community. It was built inside the community by active Claude users trying to make Claude Code more usable in real life.

We now serve a community of more than 1,000 developers who use the product to:

• monitor long-running Claude Code tasks from iPhone
• approve prompts while away from their desks
• keep work moving during meetings, commutes, and daily life
• stay engaged with Claude Code workflows without staring at a terminal

These are Anthropic customers. We are Anthropic customers too.

We are not attacking the ecosystem. We are contributing to it.

That is why this complaint is disappointing. A company that benefits from passionate developers building around its tools should be cautious about sending the message that companion-product builders will be treated as adversaries instead of contributors.

4. Third-party tooling should be seen as ecosystem strength, not brand contamination

Modern software platforms grow because communities build around them.

Developers create:

• clients
• plugins
• dashboards
• wrappers
• mobile companions
• workflow automation tools
• analytics and monitoring layers

That kind of experimentation is not a threat by default. In many cases, it is one of the clearest signs that a platform matters.

We believe Claude Code deserves that kind of ecosystem.

If every serious companion tool is met first with legal hostility instead of dialogue, developers will get a clear message: build around this platform at your own risk.

We do not think that is good for users. We do not think that is good for the ecosystem. And we do not think that reflects the posture a developer-facing AI company should want to project.

5. Our position

Our position is straightforward:

• We disagree with the complaint.
• We believe the product was built in good faith.
• We believe it serves real Claude users and adds real value.
• We do not believe common-name usage should be treated as absolute ownership across all software contexts.
• We believe companion tools should have room to exist in healthy ecosystems.

We are continuing to review our public presentation carefully, because clarity matters. We do not want users to be confused about what is official and what is independent.

But we also will not pretend that building useful third-party software for a developer ecosystem is something shameful or illegitimate.

To our users

Thank you for supporting this project.

If you are one of the developers who has used Claude Remote, shared feedback, filed bugs, requested features, or recommended it to others: this product exists because of you.

Whatever happens next, we remain proud of what this community has built together.