Skip to content

feat: add TrustClaw template#1476

Open
sarahsimionescu wants to merge 5 commits intovercel:mainfrom
sarahsimionescu:add-trustclaw-template
Open

feat: add TrustClaw template#1476
sarahsimionescu wants to merge 5 commits intovercel:mainfrom
sarahsimionescu:add-trustclaw-template

Conversation

@sarahsimionescu
Copy link
Copy Markdown

Description

Adds TrustClaw as a template — a self-hostable personal AI agent built on Composio's tool router. Two deploy paths in the README: Vercel deploy button (standard, manual env entry) and our published @composio/trustclaw CLI which auto-provisions Postgres + Redis and walks through Composio/Telegram setup.

The canonical source lives at ComposioHQ/trustclaw; this is a snapshot copy.

Demo URL

https://trustclaw.vercel.app

Type of Change

  • New Example

New Example Checklist

  • 🛫 npm run new-example was used to create the example
  • 📚 The template wasn't used but I carefully read the Adding a new example steps and implemented them in the example
  • 📱 Is it responsive? Are mobile and tablets considered?

The pnpm new-example checkbox is unchecked because plop scaffolds a vanilla Next.js + Tailwind v3 app, while we have an existing app with Prisma, Better Auth, and Tailwind v4. Following the manual checklist instead is the documented alternative.

Adds solutions/trustclaw - a self-hostable personal AI agent built on
Composio's tool router. Two deploy paths in the README: Vercel deploy
button (standard) and the published @composio/trustclaw CLI which auto-
provisions Postgres + Redis and walks through Composio + Telegram setup.

Canonical source: https://github.com/ComposioHQ/trustclaw
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
mintlify-docs-rewrite Error Error May 7, 2026 1:52am

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 7, 2026

@sarahsimionescu is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 7, 2026

Deployment failed with the following error:

The `vercel.ts` schema validation failed with the following message: `rewrites[0]` missing required property `destination`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

Copy link
Copy Markdown
Contributor

@vercel vercel Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional Suggestion:

getAuthenticatedInstance throws TRPCError in a plain Next.js route handler, causing unhandled 500 errors instead of proper 401/404 responses for unauthenticated or instance-less users.

Fix on Vercel

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 7, 2026

The Vercel deploy button now installs Neon Postgres (required) and
Upstash Redis (optional, skippable) via the marketplace, auto-injecting
DATABASE_URL and REDIS_URL into the project. Drops DATABASE_URL from
the manual env prompt - now only BETTER_AUTH_SECRET, COMPOSIO_API_KEY,
and CRON_SECRET need user input. Updates env vars table to clarify
which are auto-injected vs user-provided.
Update the deploy URL's envDescription so the Vercel deploy form shows
users the exact command to generate BETTER_AUTH_SECRET and CRON_SECRET
('openssl rand -base64 32') and the link to grab a free Composio API
key, right next to the input fields. No more hunting for instructions
in the README.
Vercel's deploy of the template ran 'pnpm build' which triggered
next-lint with our local flat-config eslint.config.js, hitting two
@typescript-eslint/no-unsafe-* errors in setup.ts. The natural fix
(eslint-disable-next-line comments) was rejected by vercel/examples'
root husky pre-commit lint because root config doesn't load typescript-
eslint plugin and treats unknown rules as errors.

Resolution: set eslint.ignoreDuringBuilds = true in next.config.js so
production builds don't run lint. Lint still runs at commit time via
husky and as an explicit step in the canonical ComposioHQ/trustclaw
repo's CI.
…st deploy

Vercel deploys the template build script before runtime, and the
Neon marketplace integration injects DATABASE_URL into the build env.
Adding 'prisma db push --accept-data-loss' between 'prisma generate'
and 'next build' means: on first deploy, the freshly-provisioned Neon
DB gets the trustclaw schema applied before the app starts. On
re-deploys with no schema changes, db push is a no-op.

Pattern adapted from vercel/ai-chatbot's 'tsx lib/db/migrate && next
build' approach.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant