Can’t get this test images away after some debugging and spending quit some credit😅 #shakespeare nostr:nprofile1qqsgvxzpp84wjd7c6mucpd9qk3k6fmcdnql2meqracd5czmtmc3ck3cpz4mhxue69uhkg6t5w3hjuur4vghhyetvv9usdz6n9a nostr:nprofile1qqsfxfs52ud0ewk569apj8hzs83ea6amgxunlty0mpuzjc32avgj7ngprpmhxue69uhkummnv3exjan99eshqup0wfjkccteqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj79q0wzz nostr:nprofile1qqsfxfs52ud0ewk569apj8hzs83ea6amgxunlty0mpuzjc32avgj7ngprpmhxue69uhkummnv3exjan99eshqup0wfjkccteqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj79q0wzz

https://nostr-react-toolkit-bzcv.shakespeare.to/marketplace

Everything else works perfect👌

Reply to this note

Please Login to reply.

Discussion

Oh my, this is likely the same issue as with filtering events I'm the feed. If you haven't already, the prompt to try would likely be akin to - "For the media assets page, we need to filter by authorized authors in our query. This query should follow a similar pattern to the one used in the review feed."

As for the session/credits issue, thank you for the heads up! How many credits were lost in your session? I'll see if we can remedy this issue.

Thanks for the answer. i will try it.

For credits hard to say I got it I think 1 x with traveltelly and 2 time with nostr:nprofile1qqsy8w40ps5wdna3jkchacyrux0t8f90m7k9fkdkhtchqfcw6xf7xnqpz4mhxue69uhkummnw3ex2mrfw3jhxtn0wfnsz9mhwden5te0vdex2ct5wghxummnw3ezuamfdejsu8tnvd Maybe you can see it back. Still love building of course but credits goes fast 😅

It worked 🙏 Thanks 🫂 Let me know if you can find the crash time can recover for now I al all set do add media to the site 🚀

https://nostr-react-toolkit-bzcv.shakespeare.to/marketplace

Ah, yes! Refresh on your side, you should be credited $30 USD to your account. This is an estimate based on your recent posts, let me know if you encounter any further issues!

Thanks! Yes last hour 😅 note1vd9awxhtr3w7fltzpsgltc4sylhjdzas454h69l9h7nlmdpwzp0s23vpj6

Thank you for sharing!

There are two probable causes for this behavior. There is a bug I'm currently investigating regarding the service provider being restarted and affecting any pending/active sessions, which could be related.

The other behavior, which is more so 'expected', is that after interacting with an agent for a long duration, it will reach a limit within its context window. The only way to move forward from that state (at this time) is starting a new session (similar to what you have described).

This is a long-term item that I believe is being investigated, and the eventual outcome would ideally be that the user doesn't have to worry or handle any issues related to the context window being hit.

That being said, to your note, the actual project code is unchanged even if that immediate session is lost; the quickest way forward is to start your chat with "we were working with X/Y/Z feature, please review our progress in the codebase and continue".

In either case, I know that nostr:nprofile1qydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qqgrcrg2jwp2lwnqlwq3s7ypcgcymx32glz4k5znv4f6qykp8l876u5t77atk is actively working to improve the overall user experience for Shakespeare. I very much appreciate your feedback at this stage, and am excited to see the things being built right now. I hope you may continue to enjoy building things out using Shakespeare, and we'll continue working to provide the best tool for the job. 🙂

🙏🫂

I know the console get to big but I can’t empty it 😥 so I got this again in middle of prompt so lost some credits again😅😥 nostr:nprofile1qqsfxfs52ud0ewk569apj8hzs83ea6amgxunlty0mpuzjc32avgj7ngpr9mhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5q32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tc8z075g nostr:nprofile1qqs8sxs4yuz47axp7uprpugrs3sfkdz5379tdg9xe2n5qfvz070a4egprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqg4waehxw309aex2mrp0yhx6mmnw3ezuur4vgzaq60d

When doing same prompt again it need to search first again the site to see how structure is so it looks like It need to do things again😥

I feel you, that can be frustrating. There a few different changes required to improve the user experience here - the ability to commit and roll back changes, the ability to reuse prompts, summary of the last session if a new one must be created, and so forth.

These interactions technically exist via the command line using the `stacks agent` tool and `git` directly, it is just a matter of translating these workflows to the Shakespeare UI. This will happen, but it will take some time to implement and test.

I understand. Hope in the long run also credits go less fast🤣🙏