[billconan]

but if say I have a long shell script, or I have a long build job failed middle way, can it locate the relevant errors in the log?

[szgupta]

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-click!)

Often times, when these longer scripts / build jobs fail, they'll emit an error at the _end_, so sharing the tail should work in this case. But, you can always tweak (add / subtract) from what you want to share with the AI to make the query even more focused.

Does that address your use-case?

[billconan]

Ya. It's just in some situations, an error triggers a series of other errors. For example, in an exception handler, there could be a follow-up error.

So often, the first line of error is where I need to look. But for a long log, locating it is not that easy.

[szgupta]

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.