Can the a view input an actual search term instead of a field filter?

Thanks for this great module.

The example views provided accept as input an exposed field filter (eg. Content: Body). But this actually filters field content rather than consults the search index, so the autocomplete results are quite different from what you get if you submit a term through to eg. node/search. Is it possible for a view used by this module to actually work with the search contextual filter as input, so the same index is consulted for both autocomplete and results?