Enough AI copilots, we need AI HUDs

Post by mellosouls » Mon, Jul 28, 2025, 10:29 AM UTC

smolder wrote: post #132

smolder wrote: post #125

Earlier quoted context omitted.

Nope, not surprising. Parent changed their text but they are just as wrong.

[flagged]

Post by [deleted] » Mon, Jul 28, 2025, 10:49 AM UTC

yahoozoo wrote: post #172

kevinphy wrote: post #145

This whole Copilot vs HUD debate instantly brought to mind a classic Japanese anime from 1991 called Future GPX Cyber Formula ( https://en.wikipedia.org/wiki/Future_GPX_Cyber_Formula ). Yeah, it’s a racing anime set in the then-distant future of 2015, where cars come with full-on intelligent AIs. The main character’s car, Asurada, is basically a "Copilot" in every sense. It was designed by his dad to be more than jus…

Anywhere to stream this?

Post by juped » Mon, Jul 28, 2025, 10:54 AM UTC

gklitt wrote: post #6

keyle wrote: post #2

> anyone serious about designing for AI should consider non-copilot form factors that more directly extend the human mind. Aren't auto-completes doing exactly this? It's not a co-pilot in the sense of a virtual human, but already more in the direction of a HUD. Sure you can converse with LLMs but you can also clearly just send orders and they eagerly follow and auto-complete. I think what the author might be trying t…

Author here. Yes, I think the original GitHub Copilot autocomplete UI is (ironically) a good example of a HUD! Tab autocomplete just becomes part of your mental flow. Recent coding interfaces are all trending towards chat agents though. It’s interesting to consider what a “tab autocomplete” UI for coding might look like at a higher level of abstraction, letting you mold code in a direct-feeling way without being bogg…

Post by OJFord » Mon, Jul 28, 2025, 11:12 AM UTC

Post by irthomasthomas » Mon, Jul 28, 2025, 11:23 AM UTC

newswasboring wrote: post #126

ijk wrote: post #79

Earlier quoted context omitted.

I want that in an editor. It's also a good way to check if your writing is too predictable or cliche. The perplexity calculation isn't difficult; just need to incorporate it into the editor interface.

Can you elaborate on how would one do this calculation?

    import openai, math, os, textwrap, json, sys
    query = 'Paris is the capital of'  # short demo input
    os.environ['OPENAI_API_KEY']       # check key early
    client = openai.OpenAI()
    resp = client.chat.completions.create(
        model='gpt-3.5-turbo',
        messages=[{'role': 'user', 'content': query}],
        max_tokens=12,
        logprobs=True,
        top_logprobs=1
    )

    logprobs = [t.logprob for t in resp.choices[0].logprobs.content]
    perplexity = math.exp(-sum(logprobs) / len(logprobs))
    print('Prompt: "', query, '"', sep='')
    print('\nCompletion:', resp.choices[0].message.content)
    print('\nToken count:', len(logprobs))
    print('Perplexity:', round(perplexity, 2))

    Prompt: "Paris is the capital of"
    
    Completion:  France.
    
    Token count: 2
    Perplexity: 1.17