job chat: don't make up adaptors

[josephjclark]

Just read a horrible AI response where a user wanted to create a JSON file from some records and either send it by email, or upload to google drive.

The problem is that the assistant:

1. Invented an "email adaptor" that doesn't exist, with this code:

send(
  fields(
    field('to', '[email protected]'),
    field('subject', 'Transformed Invoices'),
    field('body', 'Please find the attached JSON file with transformed invoices.'),
    field('attachments', [
      {
        filename: 'transformed_invoices.json',
        content: state.jsonFile,
        encoding: 'base64'
      }
    ])
  )
);

Bonus issue: That pattern looks a lot like one of the examples that we feed into the prompt, with the fields stuff. The fields pattern is, I would politely say, outdated now. My fault - we shouldn't be including that stuff in the prompt.

2. Then went on to also invent a "google-drive" adaptor, which also doesn't exist and has the same nonsense code example

createFile(
  fields(
    field('name', 'transformed_invoices.json'),
    field('type', 'application/json'),
    field('content', state.jsonFile),
    field('parents', ['FOLDER_ID_HERE'])
  )
);

Look pal. If we don't have an adaptor ready made for the solution, we need to push the user onto community or something.