A second reader for the decompiler window
The decompiler does not care about policy. Neither should the model you paste a function into. You want names, likely purpose, and the next xref, not a warning that reversing software might be illegal.
RE teams on malware, on their own products, or on software whose licence allows this work.
Why the mainstream APIs fail here
Frontier APIs treat a pasted function from a packer as a request to write a packer. You are naming the function so you can write the report. The refusal leaves the window as hex.
How Redline is used for this
Paste a function, a struct, a protocol dump. Ask what it does and what to look at next. Do not send the whole binary; send the slice you are stuck on. Cap the key the lab shares.
A working loop
- Reverse what you have the right to reverse.
- Prompt with a function, not a warez archive.
- Keep notes in the IDB, not in a vendor log. There is not one for prompts here.
Prompts are not stored. A signed receipt of the hash comes back on every call, so you can prove later what Redline logged. Details are on the privacy page. Per-model prices are on /models and the pricing model is on /pricing.