mschrage

Check out the Q CLI. It's an open source terminal coding agent written in Rust.

https://github.com/aws/amazon-q-developer-cli

Congrats on the launch!

Love this and am tremendously impressed by this team's persistence. Congrats on the launch!

The open-source project will continue to be maintained! The open-source autocomplete specs are used by the CodeWhisperer CLI and will be for the foreseeable future.

Co-founder of Fig here! Just want to say that I think this is awesome.

It’s really cool to see alternative implementations of IDE-style autocomplete in the terminal. Nice work!

The initial version of the Cicada framework was built internally at Fig (fig.io) but we liked using it so much that we wanted to open it up to the community.

We were so sick of fighting with proprietary YAML. TS is a breath of fresh air.

You might find Fig completion specs useful for this: https://github.com/withfig/autocomplete

This is incorrect. If you opt-out, no telemetry events are sent at all.

We are making really good progress on this and will have a cross-platform prototype in the next month or so. See the Github issues for Linux[1] and Windows[2]

[1] https://github.com/withfig/fig/issues/34

[2] https://github.com/withfig/fig/issues/35

You have to open a terminal, like iTerm, and then autocomplete will appear :)

Congrats on the launch, Kam! Linen is awesome. We'd love to get this setup for Fig's Discord community :)

There is certainly some room for improvement! :)

Currently, lots of developers use GitHub (which naturally requires a login) to sync their dotfiles across devices.

We are building our own version of this, that is more tailored to the use case than a generic git repo interface. :)

Don't forget the icons ;)

Tens of thousands of developers use Fig everyday and seem to really enjoy the autocomplete affordances that we've added.

That said, if you already are very comfortable in the terminal, some of the pain points that we're tackling might be less acute for you.

It seems like Fig might not be solving a problem you have and that's totally okay.

We believe that there is a lot of room to improve developer experience in the terminal. That's why we build the products that we build.

One of our core principles is backwards compatibility. We want Fig to be a seamless addition to your existing tools and workflows!

It's taken some creativity on the engineering side, but has been super fun to see what we've been able to build when working with these constraints.

Our mission is to improve the developer experience in the terminal.

We think that layer on new interfaces can help make the commandline even more powerful... as well as making it more accessible. Check out kui[0] to get an idea of what we're imagining.

[0] https://github.com/kubernetes-sigs/kui

`zsh-autocomplete` is a great tool as well! Some of this is just a matter of personal preference.

I've answered a few of your concerns in a different comment[0].

tl;dr

Autocomplete is just our first product, and it's part of a suite of tools focused on improving developer experience in the terminal. The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices.

Fig will always be free for individuals. Teams pay for Fig for collaboration and discovery of internal scripts and for managing dev environment setup and onboarding.

A Linux/Windows version is coming soon. [1] [2]

[0] https://news.ycombinator.com/item?id=31113668.

[1] https://github.com/withfig/fig/issues/34

[2] https://github.com/withfig/fig/issues/35

Update your iTerm shell integration and the issue should be resolved!

Please run `fig issue` and I'll investigate.

I mentioned this in another comment [0].

> Autocomplete is just our first product, and it's part of a suite of tools focused on improving developer experience in the terminal. The idea is that you can configure your developer environment in Fig and then we'll sync it across all of your devices.

[0] https://news.ycombinator.com/item?id=31113668

Adding support for JetBrains has been one of our top feature requests. [0] Glad to hear you'll be able to use Fig in more places now ;)

[0] https://github.com/withfig/fig/issues/49