Skip to content

Upgrade to latest dexto fails due to breaking config validation in existing ~/.dexto #487

@RajeshKumarS

Description

@RajeshKumarS

Upgrading to the latest dexto via npm i -g dexto results in a configuration validation failure on startup:

dexto
13:27:30 ERROR: Agent config validation error: {"issues":[{"code":"invalid_union","unionErrors":[{"issues":[{"code":"invalid_type","expected":"string","received":"object","path":["systemPrompt"],"message":"Expected string, received object"}],"name":"ZodError"},{"issues":[{"code":"invalid_union_discriminator","options":["static","dynamic","file"],"path":["systemPrompt","contributors",2,"type"],"message":"Invalid contributor type. Expected 'static', 'dynamic', or 'file'. Note: memory contributors are now configured via the top-level 'memories' config."}],"name":"ZodError"}],"path":["systemPrompt"],"message":"Invalid input"},{"received":"event-based","code":"invalid_enum_value","options":["manual","auto-approve","auto-deny"],"path":["toolConfirmation","mode"],"message":"Invalid enum value. Expected 'manual' | 'auto-approve' | 'auto-deny', received 'event-based'"},{"code":"unrecognized_keys","keys":["starterPrompts"],"path":[],"message":"Unrecognized key(s) in object: 'starterPrompts'"}],"name":"ZodError"}
❌ Configuration Error:
• systemPrompt: Invalid input
• toolConfirmation.mode: Invalid enum value. Expected 'manual' | 'auto-approve' | 'auto-deny', received 'event-based'
• config: Unrecognized key(s) in object: 'starterPrompts'

After deleting ~/.dexto, reinstalled dexto. It started working normally.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions