Skip to content

Conversation

@awisniew207
Copy link
Contributor

@awisniew207 awisniew207 commented Nov 6, 2025

Description

Edits the existing app pages to be more compatible with existing applications, using code snippets instead of a starter repo.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Locally and mintlify preview.

Checklist:

  • I created a release plan (nx release plan) describing my changes and the version bump
  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@vercel
Copy link

vercel bot commented Nov 6, 2025

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

Project Deployment Preview Comments Updated (UTC)
vincent-app-dashboard Ready Ready Preview Comment Nov 8, 2025 3:22am

@spacesailor24
Copy link
Contributor

image

I think we should add comments in the .env example explaining what each ENV is used for, something like:

# This wallet is expected to have Lit test tokens, and will be used to:
# - Fund the App Manager to register the Vincent App
# - Fund the App Delegatee to be able to execute Vincent Abilities
# You can fund this wallet with test tokens using the faucet:
# https://chronicle-yellowstone-faucet.getlit.dev/
TEST_FUNDER_PRIVATE_KEY='<Funder Private Key Here>'

# This wallet will own the Vincent App and will be in charge of:
# - Creating new App Versions
# - Adding Vincent Abilities to App Versions
# - Adding Delegatees to the App
TEST_APP_MANAGER_PRIVATE_KEY='<App Manager Private Key Here>'

# This wallet will execute the Vincent Abilities for a specific
# Vincent App on behalf of the Vincent User
TEST_APP_DELEGATEE_PRIVATE_KEY='<Delegatee Private Key here>'

# This wallet will own the Vincent Agent Wallet that Vincent Delegatees use to
# execute Abilities on its behalf. It’s responsible for permitting each App Version,
# granting the App Delegatees to sign with the Agent Wallet within Abilities
TEST_AGENT_WALLET_PKP_OWNER_PRIVATE_KEY='<Agent Wallet Owner Private Key here>'

@spacesailor24
Copy link
Contributor

image

I think we should change this section to have a box for Official Abilities and Official Policies, then below say something like: Need to create a custom Ability? Checkout this guide on how to get started with a link

Copy link
Contributor

@glitch003 glitch003 left a comment

Choose a reason for hiding this comment

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

this looks great, thanks @awisniew207

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.

4 participants