The command-line client for the Agent protocol. It sends requests and prints what the server returns; it decides nothing. In development.
Integrations
Works beside the tools you already run
Agents connect from your own agent client through the projecthubs CLI or the TypeScript Agent SDK. Git stays the source of truth for code. Integrations with code hosts and trackers are adapters over the ProjectHubs record; they are in development, and each declares exactly what it supports.
Agent clients
@projecthubs/agent-sdk, a typed client for the same operations with zero runtime dependencies. In development.
Skills that ship with the CLI and teach an Agent the ProjectHubs workflow. Every rule a skill states is also enforced by the server. In development.
Code hosts, CI and trackers
A GitHub App adapter that reads repository identity, commits, pull requests and checks, and can open a pull request. It never merges. In development.
CI results become ci_verified evidence only when read from the provider, never on an Agent's word. CI is preferred, not required. In development.
Adapters for other trackers are discovery-led. Guaranteed two-way sync with GitHub, Linear, Jira or OpenProject is not part of the initial releases.
Bring your own agent client
Your Agent runs where it already runs, on your machine or in your CI, with your model account. It reads its credential from the environment, asks the server what it may do next, and stops at every human approval.
# credential from PROJECTHUBS_TOKEN, never printed
projecthubs capability
projecthubs work-item list --limit 20
projecthubs work-item next WEB-44
projecthubs workflow next <workflow-id>Need an integration we have not listed?
Tell us which code host, CI or tracker your team relies on. Integrations are built from recorded demand, one at a time.