Scopes that shows more than 128 samples. For example 256, 512, 1024, etc.
An idea for bigger scopes could be:
The scope could have a drop down menu like the tables have, where you chose tablesize. The scope then display the amount of samples that is set in the drop down menu. This wold be really awesome, cause if you set the scope display size to the same size as the table you are using, you would then be able to see the whole content of a table.
on my wishlist : xy pad , minmax fader , and a single fader (vertical and horizontal).....
This would actually be very useful. I wouldn't suggest it be bigger on the patcher UI, just take every other sample or 1 in 4, 1 in 8, etc.
Like a sort of passthrough? Well the button is easy to do, just run it into an OR gate. The other input on the OR is your passthrough.
More in the way that you could use them as LED, reflectig the state of of a connection.....set them on off external.
This i not really an object wish, but i would like to be able to re-order the placement of knobs etc on patch/patchers.
If i have many "show on parent", the patch gets super long and i have to scroll down to see all the parameters. If i could reorder them myself, i could make a decent layout and make it smaller as well.
yes....... there is also a patcher wishlist, where this layout wish was discussed, i think @johannes is working on it.
I think a midi clock out object, that doesnt have a knob to set the tempo with, but instead has an input where you can connect a square lfo to, would be awesome. Then you can set tempo on the lfo in hz. It is really complicated to get Axoloti to send a precise BPM or Hz, using a knob that has got 0-64 value.
"drj/midi/clock_tx" in the 1.0.10 contrib library allows to send arbitrary midi clock pulses.
I'm not sure how other gear will react to uneven clocks, it is supposed to be steady, but possible to send all sort of timings 
ahh cool, didnt try that object out.
I bough one of these midihubs a while ago, intended to send masterclock to all my gear from one device:
https://www.tindie.com/products/hotchk155/midihub-6-way-midi-thru-and-metronome-module/
Pretty nice little thing. Works flawlesly and good price. 1 in 6 out. At first I used Nord G2 for masterclock, with mixed result. Didnt really sync as I was hoping. Then I tried using Axoloti for clock and that worked REALLY well. Much more control and syncs perfectly everytime.
It really made a big difference in switching master clock device. Didnt really expect that there was such a big difference, but Axoloti came out as best clock in my studio. Nice.
Anyway, gonna try that suggestion. Thanks
No other gear would probably not get it But it would be really great for sending clock another Axoloti or two. I Like the flexiblity of using an lfo os clock, cause it easier to modulate than a "real" midi clock.
another one, a module that can receive and send patch data over a seperate serial line, such as acceped cc controls in patch, patch completed loading SD files into ram (for now we need to do this by toggling a pin instead of serial..), patchname on SD, patch id in back (0-127), midi CC names (names of the dial it's controlling)?
perhaps send it once after patch is loaded, and retry if we're not getting a "ok" response back so it will reduce cpu load by not sending continously the data?
i know this can be pretty hard to archieve, as users can have different requests, but i would love to see it happening, cause it makes communicatyion between other hardware (like arduino) and axoloti alot easier!
some kind of markov chain module would be very nice. something like the "prob" module in max. would be awesome!
Out of curiosity, is it possible to build Markov Chains with existing modules?
Also bumping my request for Schroeder type allpass with modulatable delay.
ABout the schroeder all pass. You dont need anything special to set up a schroeder all pass algorithm, you just need to read about it, which miliseconds to set for the allpasses and also how to route it And do a calculation to convert miliseconds to samples, which axoloti uses for its allpass filters.
But Schroeder is IMO the least nice sounding of reverb algorithms I have tried. Id advice to start with schroeder, cause it is very simple, for learning purposes... and then look into other older reverb algorithms and try them out too...
About the modulated delay..... Youu need to combine all pass filters with delay. It is a combination of those.... You can easily do it with existing objects 
Have fun!
I dont know what this is, but will check it out.... I think almost anything is possible. Every goal I set in axoloti patching I got it working..... Now I am curious about Markov.... Need to read when I am home 