Repository navigation
Found by running pots init from npm on a fresh Ubuntu server without a desktop, from the first command to a reply in Slack.
Fixed
- Sign in with ChatGPT works. It stopped with "requires a device ID (UUID)".
pots initnow passes pi's own ID for this installation, as the pi command line does, and keeps it in pi's settings. - A sign-in that finishes in the browser no longer leaves "paste the redirect URL" waiting in the terminal, in the way of the next question.
- The bots keep running after you log out of SSH. Where Linux does not let a user turn on lingering,
pots initnow does it withsudo(without a password), and otherwise says the command to run. pots init --modelchecks that pi can use the model, and tries it, before it makes the bot. It used to make a bot that failed on its first wake when the model had no login or key, did not answer with that login, or its name was wrong.- No SQLite warning in the middle of the first question on Node releases that still call
node:sqliteexperimental, such as 24.13.
Changed
pots inittries the model you choose before it makes the bot. A login does not unlock every model of its provider: a ChatGPT account cannot use every OpenAI model. When the model does not answer, init says why and asks again. After a sign-in, pi's default model for the provider comes first, marked "(recommended)", when it answers with that login.
What's Changed
- pots init on a fresh server: ChatGPT sign-in, withdrawn prompts, recommended model, lingering by @Crokily in #7
- pots init --model checks that pi can use the model by @Crokily in #8
Full Changelog: v0.3.1...v0.3.2