Hi there, thanks for the mod :) I really like seeing stuff like this where folks are building new systems around the new systems.
Big space-age_mind-explosion.gif energy!

I'm wondering if it's possible to add a setting where I can remove the limitation of provider / requester chests only operating once a full stack is available for import / export. Not sure if there are performance implications (100s of tiny requests vs. fewer large requests) but I figured I'd throw it out there.

I'll put it on the list to maybe figure out. It's technically possible, of course, but since I want to limit chests to one slot to prevent people from just using them as storage, I can really only safely have one stack (full or otherwise) in transit at a time per requester or else it might have nowhere to go.

I do want to figure out some solution for sending over asteroid chunks faster though, and this is (tangentially) related, so it might work into that.

I think it would be incredibly flexible if you made it circuit triggerable when the stack is "available"

As in, don't send items unless a circuit condition is true?

Definitely a neat idea but I don't know that much about creating custom circuit logic. I'll think about it at least!

I hacked together something that lets one use a constant combinator to tell the provider a new minimum batch to send. Basically if the chest receives a signal with the same item type that is in the chest, then it uses the signal value as the minimum batch size. I need to test out the code a little more, but I can send it to you if you are interested. It's not a great interface since the user has to set up circuit networks instead of just specifying a count in the chest, but at least it works if you have something like Cryogenic Plants and you want to send one or two instead of 20.

Came here to mention this. I'm finding it a little silly that I need to send over 10 nuclear reactors at a time and can't just transfer one. This was the very first thing I tried to use your mod to accomplish, and it took me a while to figure out why it wasn't working. Must have read the full stacks part of your description, brain went "well yeah, that'll almost always be the case, no need to remember that," and then had it literally be a problem on my first usage.