openclaw - 💡(How to fix) Fix Bug: sessions_spawn fails with 'unexpected property spawnedBy/workspaceDir' [1 comments, 2 participants]

Error returned immediately. Gateway log shows:

Fix Plan

To fix the issue, we need to update the validation schema to include the spawnedBy and workspaceDir properties.

Code Changes

We can achieve this by modifying the validation schema in agent-BeieZAG2.js as follows:

const validationSchema = {
  // ... existing properties ...
  spawnedBy: { type: 'string' },
  workspaceDir: { type: 'string' },
  // ... other properties ...
  additionalProperties: false
};

Alternatively, we can set additionalProperties to true to allow any additional properties:

const validationSchema = {
  // ... existing properties ...
  additionalProperties: true
};

However, this approach may reduce the effectiveness of the validation.

Configuration Changes

No configuration changes are required for this fix.

Temporary Workaround

If the fix cannot be deployed immediately, a temporary workaround is to remove the spawnedBy and workspaceDir properties from the agent params before validation.

Verification

To verify that the fix worked, call sessions_spawn from the main agent session and check that the subagent session spawns successfully. The gateway log should no longer show the INVALID_REQUEST error.

Extra Tips

• Make sure to test the updated validation schema thoroughly to ensure it does not introduce any new issues.
• Consider adding additional validation for the spawnedBy and workspaceDir properties to ensure they conform to the expected format.