Eddie Campbell

Home / CV / Contact / Switch to light mode

Solving a puzzle with OpenCode - part 4

So far

The first three parts of this journey saw us nudge the Big Pickle LLM through solving a text wrangling / data obfuscation puzzle from a few years ago. We have been using Open Code to interact with the model, and have been asking for write ups at the end of the section.

And now

The objective now is to see if the previous articles and write-ups provide enough context for the same puzzle to be solved end to end in a single prompt… The same puzzle seeded with different secrets that is!

The two levers in the puzzle seen in previous parts were:

  1. A passphrase displayed in a .png image, that unlocked steganography data.
  2. A GPG passphrase in scrambled figlet ASCII art.

A snapshot of the puzzle generation script, showing the new target phrases is below.

Note the inconsistent use of quote styles in lines 3 and 4, outing this as an artisanal, hand-crafted, pre-LLM effort.

(⬆ new seeds for puzzle)

One last time

In previous parts solving would cease due to the model requesting permission to sniff about my local disk. I’m looking for a hole in one here, so have put in contingency. Don’t let me down Big Pickle!

(⬆ part 4 prompt)

Quick results

Some interesting results straight out of the gate - we are in figlet territory already.

(⬆ fast results)

I found it genuinely difficult to watch from excitement!

Near miss

Before much longer, the figlet text looked very close to being descrambled but the output suggested that it might be going in a dictionary attack direction.

(⬆ nearly there)

Heading off the rails

Disappointment started setting in when seemingly random phrases were being checked.

(⬆ dearie me)

All of the hacker movie tropes are here now.

(⬆ various password tropes)

Compaction and hallucinations

I came back just shy of 4hr later and witnessed a compaction in progress.

Objective

Requirements

Decisions

That conviction in that last part was worrying - the passphrase hidden in the figlet was NewSecret!!!. There appeared to be a hyperfixation on the “…rule the world” clue intended for humans, despite its throwaway nature being clarified in the earlier posts. The compaction really baked this in.

The end of the road

Having left things alone overnight I returned to a sight I had yet to see during my OpenCode escapades. It was not clear at which point during the nearly 11hr left alone the tokens had been exhausted, but exhausted they were.

(⬆ achievement unlocked)

I was able to ask another model, Flash v4.1 free to generate a README as in previous parts.

Conclusions and next steps

I was optimistic going in that our previous posts and write-ups would be enough to provide a solid context to solve the puzzle in a single prompt, but it wasn’t to be. By specifying up front that the local disk was off-limits kept OpenCode in its lane, which was a change from previous parts, and allowed for an unattended approach until such time as the free message limit has exceeded.

While this is an unsatisfactory conclusion, I feel we have seen some real flashes of excellence in the experiments that lead up to this point. The free model was highly capable of solving non-trivial problems in isolation when guided toward them - it just wasn’t able to replicate these in an end to end situation.

I hope you have had some enjoyment - or even learned something - from these posts on nil-cost AI products. My mind has already moved to the more mainstream players: how would the free tier Claude / ChatGPT web chat offerings fare with the same challenge in 2026?.

In the next part we will try exactly that.