CLI do Passe1 (fatia 2)
Seu passe de IA no terminal: valida a chave, conversa com streaming, lista modelos e skills, e aponta seus harnesses para o gateway.
Instalacao
curl -fsSL https://passe.dehor.com.br/cli/install.sh | sh
# depois use direto, de qualquer pasta:
passe1 login
passe1 chat "explique closures em 3 linhas"
Desenvolvedores (dentro do repo): pip install ./cli, ou rode sem
instalar com python cli/passe1.py ....
Uso
# entrar uma vez (a chave fica em ~/.config/passe1/key, modo 600)
passe1 login
passe1 login sk-passe1-...
# conversar (uma pergunta, stdin ou REPL; /sair encerra, /limpar zera)
passe1 chat "explique closures em 3 linhas"
passe1 chat
passe1 chat --model mimo-v2.5 "oi"
echo "resuma isto" | passe1 chat
# skills locais (SKILL.md do Claude/Codex ou de ~/.config/passe1/skills)
passe1 skills
passe1 chat --skill revisor "revise este texto"
# no REPL: /skill NOME ativa, /skill mostra a ativa, /skill off desativa
# (a ativa fica salva e vale para as proximas sessoes)
# /model mostra o atual, /model ID troca sem sair do chat
# modelos (com visao e janela) e status (passe, validade, uso)
passe1 models
passe1 status
passe1 models --json # saida maquina para scripts
passe1 status --json
passe1 logout
# apontar um harness para o Passe1 (faz backup do config atual)
passe1 setup claude
passe1 setup codex
passe1 setup verboo # gera ~/.config/passe1/verboo.sh, importe com source
Opções globais: --base-url (aponta para outro gateway, ex. o local) e
--versao. A variável PASSE1_MODEL troca o modelo padrão do chat.
Testes
pytest cli/tests -q # sem rede (httpx MockTransport)
Notas
- A chave nunca aparece em log nem em erro: só os 4 últimos caracteres.
- O chat usa streaming (SSE); se o gateway responder JSON simples, a CLI entende mesmo assim.
- O REPL guarda historico em ~/.config/passe1/history (setas funcionam).
setup codexpedeexport PASSE1_API_KEY=$(cat ~/.config/passe1/key)no terminal;setup verboogera snippet parasource(o Verboo CLI lê provedor por variável de ambiente).
Metadata
Release files for passe1 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| passe1-0.2.3.tar.gz | 13.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| passe1-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.7 kB
Release files / passe1-0.2.3.tar.gz
| Download URL | passe1-0.2.3.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a2e28cbba0a141dade4702b0aaee59f931eb61a21a0c51ba25d406d1c4512d0
|
|
BLAKE2b-256 checksum How to use checksums |
c5adfe626a244ae6645520d1157655e76fe9ae4deb5d829d05bd7226b75e15f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency logRelease files / passe1-0.2.3-py3-none-any.whl
| Download URL | passe1-0.2.3-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
417a1e4f2eb64a0624011c3e697ce250f801f90fbeed22454cb16d42978a23e4
|
|
BLAKE2b-256 checksum How to use checksums |
0a0ca19f7de260cd6501681a0fb603b4f1859deec80a685c7b26b2cea219b603
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency log