Use DeployHQ from Claude
Add the DeployHQ connection to a Space that runs Claude, then use it from every channel in that Space.
Create a DeployHQ connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the DeployHQ connection to a Space that runs Claude, then use it from every channel in that Space.
Add the DeployHQ connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
DeployHQ automates deployments from Git, SVN, and Mercurial, and the housekeeping side, old projects, stale build caches, outdated exclusion rules, tends to pile up quietly. A DevOps Space in type.com can ask Claude to clear a build cache, remove a server group that's no longer used, or delete an old project, keeping the deployment configuration from accumulating clutter.
Connect DeployHQ once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Remove a cached build artifact that's taking up space or causing a deploy to use outdated files.
Delete the build cache file for our staging project in DeployHQ, the last deploy pulled a stale asset.
Remove a server group from a project's configuration once that environment is decommissioned.
Delete the legacy-eu server group from our main DeployHQ project.
Permanently remove a project that's no longer deployed anywhere.
Delete the old marketing-site-v1 project from DeployHQ, we shut that site down last month.
Removes an SSH command from a project's deployment configuration.
Permanently removes a project from DeployHQ by its permalink or identifier.
Removes a cached build artifact from a project's build cache storage.
Removes an excluded file pattern from a project's deployment configuration.
Removes a server group from a project's deployment configuration.
DeployHQ offers REST and OpenAPI documentation for automating deployments from Git, SVN, and Mercurial repositories. Integrations can trigger deployments, inspect projects, manage servers and config files, wire DeployHQ into CI/CD pipelines, and use authenticated API calls or the official Ruby gem for deployment workflows.
Yes. Once DeployHQ is connected to a Space, you can ask the agent to clear a build cache, remove a server group, or delete an old project, and the change shows up in the thread for the team.
DeployHQ uses basic authentication. An admin enters the credentials once when creating the connection and controls which Spaces can use it.
Yes. A recurring cleanup, such as reviewing stale build caches monthly, can be set up as a type.com automation that posts a summary to a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Svix to Claude in type.com to create applications, check endpoint status, and manage webhooks from a shared thread.
Connect Swaggerhub to Claude in type.com to manage access control, check API versions, and update portals from a thread.
Connect Swarmsyncai to Claude in type.com to register agents, check username availability, and run marketplace discovery from a shared thread.
Connect Synthflow AI to Claude in type.com to update knowledge bases, attach actions, and manage memory stores for your voice agents.