Traycer’s Cursor extension only takes
Traycer’s Cursor extension only takes permissions to read user id and email while logging in via GitHub
15 Replies
What is that required for?
For matching the user’s identity at our end. We can’t distinguish paid user from free unless you sign in via GitHub
And the stuff the Cursor plugin does is paid-user only?
You basically generate code from the plan. And then can follow up with more tasks. It is free for open source projects with reasonable rate limits
Here’s a demo of the extension. It works standalone, not just with tickets https://youtu.be/rlev6OeLC6U?si=uTGZiWfPJPLQARLA
Traycer AI
YouTube
Traycer AI Tasks Demo by Santiago: Automate Your Productivity!
📢 Try Traycer for FREE today! https://traycer.ai 📢
Turn hours of coding into minutes with AI-powered automation! 🚀 Traycer Tasks plans, implements, and reviews every change, making project-wide updates effortless.
Watch as Santiago transforms his coding workflow using Traycer AI—an intelligent assistant that acts like both an ar...
Turn hours of coding into minutes with AI-powered automation! 🚀 Traycer Tasks plans, implements, and reviews every change, making project-wide updates effortless.
Watch as Santiago transforms his coding workflow using Traycer AI—an intelligent assistant that acts like both an ar...
Right. I was under the impression that the plan was handed off to Cursor/Windsurf. That exact video is what led me here.
I see. Do you think that would be useful. Ability to copy the plan to composer/cascade?
Sorry. I ws wrong. It was this one https://x.com/svpino/status/1915393076694274444
Santiago (@svpino) on X
Oh wow! Here is a 10x workflow to build software.
It's a full integration between GitHub and a coding assistant on your IDE:
• Report issues on GitHub issues
• AI generates a plan to address the issue right there
• The team discusses the plan (add comments, modifications)
•
X
We can easily provide a quick button that can take the plan into Cursor Composer. We have seen users do that with our extension in the past
Just for concreteness. Here's the issue on GiHub:
https://github.com/curtcox/inspector/issues/1
Traycer created the plan and there are buttons. It is the workflow I would use.
I didn't get any feedback about why the Windsurf link failed. The Cursor link appeared to work as long as Cursor was already open with the appropriate project.
GitHub
Support running locally with Deno · Issue #1 · curtcox/inspector
As a developer, I would like to be able to run inspector locally using Deno, so that I can use the Deno security features. The complete resolution of this issue should include a script that allows ...
Thanks for sharing.
We’ll double check what’s up with WindSurf. Do you have it installed? cc: @Hardik Shingala
We designed the GitHub integration to work seamlessly with Traycer’s VS Code extension.
Traycer’s IDE extension is an alternative to Cursor Composer. It keeps the developer in control with staged code changes. And manages context really well across a chain of Tasks. I recommend you give it a go.
But I understand that everyone has their go to tool for code generation so we can invest in providing a smoother transition to other Agentic execution systems like Cursor Composer
Cursor launches from the command line when when I type cursor, but windsurf doesn't. I'm pretty sure that is the difference.
So, the details of how they were installed.
Thanks for sharing those details. We’ll double check all these scenarios
Thank you!
@CurtCox, I just tried importing the above ticket on a fresh Windsurf installation, and it imported the issue correctly.
To import an issue, we use an API provided by VSCode. The API has the limitation that the extension has to be already installed on the IDE and that the IDE should also be open. So, when it failed for you, did you have Windsurf open and Traycer extension already installed in it?