Skip to content

Vincent 2.0 Dashboard#440

Open
awisniew207 wants to merge 7 commits intomainfrom
feat/vincent-2.0-dashboard
Open

Vincent 2.0 Dashboard#440
awisniew207 wants to merge 7 commits intomainfrom
feat/vincent-2.0-dashboard

Conversation

@awisniew207
Copy link
Contributor

@awisniew207 awisniew207 commented Dec 30, 2025

Summary

Note: This PR should not be merged. After review, I will split this into two PRs and handle the deployment of the new dashboard.

If we want to have the working preview deployment as part of the review process, as opposed to running this locally, please let me know. I'll have to split this PR immediately, merge the registry-backend/registry-sdk changes, and then redeploy the backend. At that point I can setup a new Vercel project and configure secure mutations + authentication from the FE to the BE. Just let me know if we'd like that.

App Dashboard

Authentication

  • Replaced Stytch/JWT authentication with SIWE (Sign-In with Ethereum)
  • Added new SignInScreen component for wallet-based sign-in
  • Added session expiration handling and user disconnect flows

App Management

  • New version management flow: Simplified from publish/unpublish model to enable/disable
  • Added SetActiveVersionForm for choosing which version users see
  • New CreateAppVersionWrapper for creating versions with abilities
  • New AppVersionDetailsWrapper and AppVersionsWrapper
  • Refactored CreateAppWrapper (~1000 lines → modular components in create-app/ folder)
  • Simplified EditAppForm, DeleteAppForm, ManageDelegateesForm
  • Added chain validation to ensure users are on Base Sepolia before on-chain operations

Removed Components

  • Deleted entire user dashboard (/user-dashboard/* pages and utils)
  • Removed old version management: PublishAppVersionWrapper, AppVersionDetailWrapper
  • Removed mismatch resolution: AppMismatchResolution, AppVersionMismatchResolution
  • Removed old button components: AppUnpublishedButtons, AppVersionPublishedButtons, PublishAppVersionButton, etc.
  • Removed old forms: EditAppVersionForm, DeleteAppVersionForm, EditAppVersionAbilityForm, CreateAppVersionForm
  • Removed utilities: lit.ts, transactionService.ts, getAgentPkps.ts, withdrawHandler.ts, etc.

Registry SDK

  • Removed deleteAppVersion/undeleteAppVersion endpoints (on-chain is source of truth)

Registry Backend

  • Added SIWE authentication middleware
  • Fixed ESLint configuration for package detection

@vercel
Copy link

vercel bot commented Dec 30, 2025

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

Project Deployment Actions Updated (UTC)
vincent-app-dashboard Ready Ready Preview, Comment Jan 30, 2026 4:27pm
vincent-dashboard-2.0 Ready Ready Preview, Comment Jan 30, 2026 4:27pm

Request Review

@awisniew207 awisniew207 force-pushed the feat/vincent-2.0-dashboard branch from 612c01b to bcf7dd7 Compare January 13, 2026 19:32
@awisniew207 awisniew207 force-pushed the feat/vincent-2.0-dashboard branch from 3afc05d to a2ac9fa Compare January 14, 2026 19:21
@awisniew207 awisniew207 force-pushed the feat/vincent-2.0-dashboard branch from a2ac9fa to 921f750 Compare January 21, 2026 00:37
@awisniew207 awisniew207 changed the base branch from vincent-2.0 to main January 21, 2026 01:08
@awisniew207 awisniew207 force-pushed the feat/vincent-2.0-dashboard branch from 2c32315 to b5a2129 Compare January 23, 2026 03:52
@awisniew207 awisniew207 changed the title Feat/vincent 2.0 dashboard Vincent 2.0 Dashboard Jan 23, 2026
@awisniew207 awisniew207 marked this pull request as ready for review January 23, 2026 04:30
@DashKash54
Copy link
Contributor

SIWE message URL is api.heyvincent.ai shouldn't it be the frontend? Otherwise the user/dev will get an alert message due to mismatch URLs?

@awisniew207
Copy link
Contributor Author

Do we have an ability with registered policies? This is not a priority though

@DashKash54 we do not at the moment. I think we'd need it to be a Vincent 2.0 ability anyways

@awisniew207
Copy link
Contributor Author

Do we have a repository of abilities that we should to all app devs when they register a new app or do they have to always first provide their own abilities?

We have a database with abilities, but it's mostly empty right now since we just initialized it. We will provide the first ability, which will be the relay.link ability

@awisniew207
Copy link
Contributor Author

When registering an Ability I got the error: "Metadata file vincent-ability-metadata.json not found in package" this is a must have in the package? So I haven't been able to test the Ability & Policy registering work flows. Do you have a demo package you've tested it with?

It is a must-have, since that file contains the IPFS CID. The ability and policy registration hasn't changed from the Vincent 1.0 dashboard, but you can use the latest versions of the vincent-demo-ability and vincent-demo-policy packages which I published myself.

@awisniew207
Copy link
Contributor Author

SIWE message URL is api.heyvincent.ai shouldn't it be the frontend? Otherwise the user/dev will get an alert message due to mismatch URLs?

I'll ensure this is fixed on our production deployment. Working on it now.

@DashKash54
Copy link
Contributor

We will provide the first ability, which will be the relay.link ability
But will it be registered in the Ability registry and shown to all the devs or everyone has to read it from the docs and copy paste the version?

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.

2 participants