layerv-ai
There is so much software to still be built!
Great to see people building open source in this space since p2p sharing gets a lot more expansive and harder to get right with AI agents.
Have you been using this with personal agents like instinct or grok bot? Would be a great way to share files without allowing full computer use/exposing more access than you have to!
We knew that what we're building is high impact for AI/agentic world due to the nature of expiring gated-access links for sharing local resources, which is not really something that our competitors (ngrok or cloudflare or tailscale) could offer as well as we could.
People were pretty excited, but when we were getting them to try out qurl and running locally, they'd run into all sorts of issue where their coding agent would get confused or distracted and wouldn't actually do the setup we needed them to do (just a few `qurl <param>` commands). It was weird because our docs were public, and github was fully searchable, so we kept wondering why the agent wouldn't just search for it and figure it out?
What we realized was that our target audience here, which were largely not-super-technical people who more so cared about vibe coding demos rather than doing proper software engineering (as that wasn't their job), didn't really prompt in the same way as software people like us did. They didn't really "know" how to talk to AI.
In particular: they prompted with one-shots and incomplete/unspecific requests, asking for things like `share my app with qurl`; the agent would intuitively know "I have to search for qurl and figure out how to use it", so it would do that; but then, it would ask random other things (to confirm) about homebrew, local setup, preferences, etc. - and since these questions were often roughly technical, many of our users would get derailed and more confused. So, they'd start a conversation with the agent instead of asking it directly, leading to both of them being confused... which would eventually lead to the agent just suggesting something like ngrok or cloudflare to unblock the user's line of questioning.
It was weird - but we tested this internally and reviewed the traces, and found that it just came down to prompting habits ultimately: AI is trying to both give you as much info as it can, be as succinct as possible, and also not assume too much about your request all at the same time. It's a REALLLY hard balance to strike. (so it makes sense that it's not perfect)
So as a result, when non-technical people were asking to deploy a qurl, the moment the agent would get stuck and need their help, they naturally wouldn't know how to answer or what it was even asking, so the simple request would spiral into its own conversation fork and the `deploy with qurl` point would get lost in context. The prompting advice we came up with for them was this: "if your agent gets stuck, just tell it to search online and figure out how to unblock itself." Because of the balance it tries to strike, it sometimes just needs that little approval to just go and look things up on the internet, even if it is wasting tokens doing so.
So the point here isn't so much that it takes skill, but rather it just takes intuition about what AI is good at/bad at and what sort of personality it's being trained to embody. Once you get the hang of that, even if you know nothing about coding at all, you can become pretty effective with your AI toolset simply by virtue of knowing what directions to guide it to and watch pitfalls out for/how to unblock it when needed.
Our 2c on the topic!
This feels what parallel to today's discussions around SEO too, where people will scream that "SEO is dead" and "I can do my own SEO in 5 minutes"... yes, it is true that you can run a 2020-era SEO strategy in 5 minutes. However, a proper 2026 SEO strategy will take you just as long as 2020 SEO used to take you in 2020 because the baseline/"goal posts" for SEO have shifted.
Expect the same thing to happen to lawyers; reviewing a contract is now 15 minutes worth of work instead of 3 hours; but that means that you can review this + that + the other contract + also go through a bunch of similar cases and look for loopholes - all in the span of 1 hour. This allows you to give your client better advice in the same number hours spent. Nothing actually changes in your business model (unless you're billing token costs separately; then maybe you have some extra bonus charges; but that seems like it'd be unpopular with clients, so probably wouldn't stick)
A cool finding we had: we tried a lot of different models - Deepseek v4.1 flash, Qwen3.8, Opus 5.5, 6.1 Sol - while testing our "agent experience" for setting up and using qURL (OSS temporary tunnels; similar to ngrok but faster to use / more private) and found that even though Deepseek and Qwen were less intuitively smart about figuring out how to use qURL, the number of tokens they spent digging through docs and figuring things out was barely 1.5x that of Claude/GPT.
This would indicate that even though these models aren't the "frontier", they're still quite capable and WAYYY cheaper (which, from an avg dev's perspecitve, is still worth it). For most consumer-grade tasks, opus is going to be overkill anyway, so eventually, I think we will really see the consumer-enterprise AI model choices split.
Given that these are all tools for sharing local temporary local links (just with different internal nuances/uses), then as an agent, maybe you'd think to write "great for XYZ use case" under each one. That'd make sense and be pretty obvious. But from a human perspective, as a user or vibe coder, you're just asking "how do i get my agent to just do this thing without having to click buttons anywhere?!" which is a very different problem.
We're truly splitting demographics here lol
And as a secondary consequence, imagine you've connected your whole life to your agent and used it for 5 years, and then your agent gets prompt injected.
Everything about you/your life is stolen and it's just straight up over
if models can find and exploit bugs this fast, anything sitting on a public IP is going to get tested harder and faster.
soon, you'll just have to live under the assumption that an attacker could theoretically get into your infra - so all your precautions will need to have that as a baseline
hence, betting on "undiscoverable resources" as the next big enterprise push!
however - agree that this is not great - espeically if chat TTL is long. someone who gets your URL can read everything you're asking (eg. by sniffing your network/accessing your browser history)