OpenFn / OpenFn/lightning

AI assistant: absorb a long paste instead of refusing it

Open
#5,138 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

Paste a long spec into the assistant today and it tells you the message is too long. That is better than what it used to do, which was nothing at all, but it is still a refusal. The person pasting fifteen thousand characters of requirements is not making a mistake; they are asking the clearest question they have.

Claude and Slack both take the paste instead. It becomes an attachment on the message, the box goes back to empty, and you type your actual question above it. Nothing is refused and nothing is lost.

We would need somewhere to keep the pasted text, a way to send it to Apollo as context rather than as the message, and a chip in the input showing what is attached with a way to remove it. The run attachments already give us most of the shape.

This supersedes the character counter added for https://github.com/OpenFn/lightning/issues/4883, which was the honest thing to do while we could not absorb the paste.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing run attachments and the character counter described in issue #4883. Trace how pasted content reaches Apollo and how the assistant input represents attachments. Done means a long paste is retained as an attachment, the input can show and remove it, and Apollo receives it as context while the user’s message remains separate.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
ai, backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.