Keep getting Runtime Error Unexpected token ‘>’ even though asking v0 Agent mode to fix the issue with more than 50 versions and still not resolved!!! Agent Mode doesn’t work at all!!! Please bring back other models!!!
https://v0.app/chat/erp-all-center-wz7Ktqf6QZh#ZSKBQPOZvcjFUilYy1ZHSwBFn2kYfEUX
I’m experiencing exactly the same issue.
I’ve had the same problem for days - whats odd its appears to have affected a certain section of my project and what really werid the issue is happening on ALL my previous Forked versions and Preview versions (same section). The AI agent cannot fix it - to me it feels like V0 have depreciated a library or something thats affected all prev forked and preview versions. God known how many credits I’ve spent to try and fix this…to no avail.
I’ve logged a case and they can’t find anything.
Downloaded the codebase and shared with Claude Code - which suggested a fix. The fix has reinstated an offline version of my V0 code but when I ask the agent to apply the same fix it doesn’t work. Have shared the Claude Code fix with V0 and logged a case - not reply
Up until now, I still haven’t received any response from the v0 team, and my project remains on hold.
I consider this to be a highly irresponsible approach, especially since the service is subscription-based and even the additional purchased credits cannot resolve the issue. Providing the old models should not be such a difficult task—so why is the v0 team ignoring customer requests? What internal problems are causing this?
What we expect is open and honest communication, not silence when faced with negative feedback. Please respond as soon as possible regarding how v0 team will resolve the issue of Agent Mode being unusable.
I’m experiencing exactly the same issue too.
Vercel Staff, when you see this message but choose not to reply, it is a very irresponsible action. At the very least, you should reply to let us know that the issue is being addressed, rather than choosing to ignore it.
Cross-posting this same discussion here for visibility as it seems to be the same issue.
Sorry to hear this! Can you share a chat example with us?
Do you have an example chat we can take a look at?
Hey folks!
Looks like it was a bug on our side, that should be fixed now.
Could I ask you all to send a new message with the following:
Find all .js and .ts files in this project that contain JSX syntax and help me rename them to have the correct .jsx or
.tsx extensions. Look for files that:
1. Import React or use React components
2. Contain JSX elements (like <Component>, <div>, etc.)
3. Have return statements with JSX
4. Use JSX fragments (<> or <React.Fragment>)
For each file found, suggest the correct new filename and provide a command to rename it. If it's a TypeScript file
(.ts) with JSX, rename to .tsx. If it's a JavaScript file (.js) with JSX, rename to .jsx.
Let us know how you get on!
hi @pawlean
Your suggestion - kinda worked for me on one of my forks - but not on any of the others.
All the other Forked versions are saying “Great news! After thoroughly searching your codebase, I found that all files already have the correct extensions. There are no .js or .ts files containing JSX syntax that need to be renamed.“
Even thought they are still tripping a Runtime error expected expression, got ‘>’
When I downloaded the code and showed it to Claude Code:
The fix that Claude Code suggested a while back was;
The issue is that the getFlagIcon function is trying to return JSX elements in a TypeScript utility file.
I need to add React import and change the return type.
Let me fix this: Update(app/jobs/utils/job-utils.ts) ⎿ Updated app/jobs/utils/job-utils.ts with 1 addition 1 + import React from “react” 2 import { AlertTriangle, CheckCircle } from “lucide-react” 3 import type { Job, JobStatus, JobFlag } from “../types/job-types”
Hi @Pauline P. Narvas
The method you provided did not work. I still get the error message Runtime Error Unexpected token ‘>’. Could you please ask the v0 team to resolve this issue as soon as possible? We have already been waiting for five days. it would be very helpful if the old model could be made available so that we may continue progressing with our project. Thank you.
Can you try with a new fork?
How about new forks?
@pawlean New fork doesn’t work. 
I really don’t want to keep wasting money trying to solve a problem that can’t be solved. Please have the v0 team fix this issue as soon as possible. Even the prompt you provided doesn’t work—how can you expect users to solve the problem themselves? It’s obvious that Agent Mode wasn’t ready. Why are you unwilling to restore the old model? Do you really care about your users? If you still don’t even know what the problem is and need to open a thread to collect user feedback—don’t bother. Just restore the old model so users can continue their projects, or quickly fix Agent Mode.
@pawlean
Have you tried it yourself? Has the v0 team tried it?
https://v0.app/chat/fork-of-erp-all-center-K100do3K4BU
