Terms

• Licence: Apache-2.0. You may use, modify, and redistribute swe-mux, including commercially, provided you keep the notices the licence requires. See LICENSE and NOTICE.
• No warranty, and limited liability. The licence's sections 7 and 8 provide the software "as is", without warranties or conditions of any kind, and limit the contributors' liability for damages arising from its use. That is the operative text, not this sentence, and it is worth reading before you run an autonomous agent against a repository you care about.
• What that means in practice. swe-mux launches coding agents with the full privileges of the account running the daemon, and executing code on that machine is its purpose rather than a defect. Back up your work, review what your agents are configured to do without asking, and keep the approval floor in place.
• Third-party components redistributed with swe-mux keep their own licences, listed in THIRD-PARTY-NOTICES.md and on the acknowledgements page. No GPL or AGPL code ships.

swe-mux launches and observes coding-agent CLIs published by other vendors, including Anthropic's Claude Code and OpenAI's Codex CLI. It is not affiliated with, endorsed by, sponsored by, or certified by any of them, and it uses their names only to identify which tool a feature works with.

• You run those CLIs under your own account and your own agreement with each vendor. The same is true of the optional OpenRouter and Hugging Face integrations, and of Tailscale if you use it to reach your machine.
• swe-mux proxies nothing and resells nothing. It does not sit between your agent and its vendor, and it holds no relationship with any of them on your behalf.
• Account switching is a convenience for one person switching between accounts they personally own and pay for. It is not account pooling and not a way around a usage limit: accounts are never shared between people, sessions are never load-balanced across accounts, and switching is always an explicit act.
• Quota, billing, and account-sharing questions belong to that vendor. Nothing here changes what your agreement with them permits.

Apache-2.0 grants copyright and patent rights and deliberately does not grant trademark rights. The practical shape of that reservation is written out in TRADEMARK.md: you may say your fork is derived from swe-mux and you may not present a modified build as though it were this project.

• swemux.dev lives in site/ in the public repository, so it is under the same Apache-2.0 licence as the rest of it.
• Every claim on it is meant to be checkable against the repository, and several pages say which file to check. If one is wrong, open an issue; it will be corrected.
• The comparison page describes other people's products from their own published documentation and carries the date those sources were read. It is not a benchmark and it is not an endorsement in either direction.
• The roadmap is direction, not commitment, and says so. A vote on a feature request is a signal, not an obligation.

There is none to buy and none promised. Bugs go to issues, feature requests to the Ideas discussions, and vulnerabilities privately through the security policy. The response times in that policy are the targets of a maintainer-scale project, stated so a reporter knows what to expect, and they are not a contractual commitment.

Only the most recent release is supported. There is no long-term support branch and no backport process; upgrading is the remedy for every reported issue.

This page is a plain-language summary of documents that are themselves the agreement. It is not legal advice, and where it and LICENSE differ, the licence governs. It states no choice of law and no dispute procedure, because the licence's own terms are what apply and inventing a second set beside them would create a conflict rather than resolve one.