szgupta

7 ms·

1. 1.▲
   by szgupta 4y ago

   Ah that makes sense. We could certainly investigate solutions to this. As a stopgap, if you see the log-line for the error in your output, you can copy just that log-line and ask Warp AI about that line specifically.
2. 2.▲
   by szgupta 4y ago

   Hey! Currently, when you share a block (grouped input and output) with Warp AI, we let the AI know the command that was ran and also the tail of the output. (and to streamline this even more, sharing a block with Warp AI is as simple as one
3. 3.▲
   by szgupta 4y ago

   Hey, thanks for the suggestion! We have plans to further integrate the shell-context so that the AI can curate its answers even better. For example, letting the AI know that you're working in bash vs. fish so the commands it suggests r
4. 4.▲
   by szgupta 4y ago

   Hi HN, I’m Suraj, an engineer at Warp (www.warp.dev) where we’re building a fast, Rust-based terminal for the 21st century. Today I am excited to share Warp AI with the community. With this launch we have added AI to the core interface of t
5. 5.▲
   by szgupta 4y ago

   Hi HN, I’m Suraj, an engineer at Warp (www.warp.dev) where we’re building a fast, Rust-based terminal for the 21st century. Today I am excited to share Warp AI with the community. With this launch we have added AI to the core interface of t
6. 6.▲
   by szgupta 4y ago

   I love this sentiment. Your questions would make for a very interesting post. While we haven't rebuilt from absolute ground zero, Warp is definitely trying to extend the capabilities of a terminal (emulator) from what's historical
7. 7.▲
   by szgupta 4y ago

   Thanks for the comment. I definitely feel your concerns. To clarify, all cloud-oriented features are fully opt-in. For example, you have to explicitly share a block for us to store it in the cloud. You can also opt-out of telemetry (which w
8. 8.▲
   by szgupta 4y ago

   Yeah I like to think of it as a capability list as well. There was a brief footnote [12] about $TERM in the post, but terminfo could certainly be dissected further. [12]( https://www.warp.dev/blog/what-happens-when-you-o
9. 9.▲
   by szgupta 4y ago

   Hey, sorry about that! We actually have a WIP fix for this exact issue (the obtrusive overlay that you can't dismiss). Should be out in the next week or two.
10. 10.▲
    by szgupta 4y ago

    Haha, yeah we probably should have added a caveat that this is only applicable to Unix
11. 11.▲
    by szgupta 4y ago

    Haha! The post was actually motivated by a common (interview) question: https://github.com/alex/what-happens-when . We thought it would make for a fun adaptation for the terminal world
12. 12.▲
    by szgupta 4y ago

    Thanks! It was fun to write this up. Glad you enjoyed :)
13. 13.▲
    by szgupta 4y ago

    Thanks! Were there any topics in the blog that you think would benefit from more detail in a follow-up post?
14. 14.▲
    by szgupta 4y ago

    Hey HN! I'm Suraj, one of the authors of this blog post. Andy (@acarl005) and I came up with the idea to write this post when we realized there weren't many existing resources on how a terminal works under the hood, end-to-end. If