Richard Woodbury

Try this with the "Mosh (dev)" version in the Chrome Web Store to see if the problem persists. It has a newer hterm (the shared terminal emulator), which may have...

You may be on to something with the version of hterm. Try the "Mosh (dev)" version in the Chrome Web Store, which is newer. I'm going to be pushing hterm-1.80...

They apparently added support in Mosh 1.3.2 (see mobile-shell/mosh#649), and that's the version being used in the latest dev release, but it doesn't seem to be working. Edit: I misread...

Edited my previous statement about mosh 1.3.2. It does _not_ include the true color commit. So this is _not_ expected to work yet.

The [default command](https://github.com/rpwoodbu/mosh-chrome/blob/63a94642999c6352b008bf186bf09f07e8034838/mosh_nacl/ssh_login.cc#L44) includes `-c 256`, but definitely if you're overriding the command, you'll need to be sure to specify that switch.

@gordallott Is this reproducible in the Secure Shell app? May be an hterm problem.

@gordallott I just tried to repro this, and I don't see this working in Secure Shell (v0.8.36.8)... in other words, I see blue lines instead of gray. I connected directly...

This support already exists, but I haven't actually documented it. It works similarly to how it does in Secure Shell, except that the agent app ID is [hardcoded](https://github.com/rpwoodbu/mosh-chrome/blob/master/mosh_app/mosh_window.js#L79), so there...

Not sure what the "SSH forward helper" is. I haven't seen anything like that. You can experiment with other apps either by editing the code and rebuilding, or poking your...

Oh, actually, I might have an idea about the "SSH forward helper" thing. I know about "native messaging", which is a facility through which Chrome can communicate with a native...