White paper
Hub William: tools and agents, shared with your team
Hub William is a place to share useful tools and agent access. Contributors can publish tools and improve existing ones, while account owners can create agent pools and share access with teammates through the gateway.
01. Why Hub William
Share access without passing around provider credentials
Sharing an account directly means handing out credentials and managing access across teammates' devices. Hub William keeps the provider connection on the server. Owners manage who can join a pool, and approved teammates use their own Hub gateway keys.
Requests pass through a shared gateway instead of requiring every teammate to sign in to the provider account from their own machine. This centralizes upstream access and makes membership and key revocation easier to manage. Provider usage limits and account policies still apply; a shared gateway does not guarantee protection from an account ban.
Agents brings connected accounts, usage and pool membership together. Tools contains setup instructions and integrations, including Gateway, OpenCode and OMP. Playground lets you try models using your connected accounts and approved pools.
02. How to contribute
Useful tools grow through contributions
Contribute a tool through a pull request. Each contributor owns a folder named after their GitHub username, with tool documentation written in Markdown.
contributors/
├── default/ # system (read-only)
│ └── tools/
│ ├── gateway/
│ ├── opencode/
│ └── omp/
└── <your-github-login>/ # your contributions
└── tools/
└── <tool-name>/
└── README.mdThe default folder belongs to the system. It is read-only for contributors: do not edit, rename or delete anything under contributors/default/. Add your own username folder instead and keep your contributions inside it.
- Fork the repository and branch from dev.
- Create
contributors/<your-github-login>/tools/<tool-name>/and add aREADME.mddescribing your tool. You can update tools inside your own contributor folder. - Open a pull request into dev with a description of the change and the checks you ran.