Your first session#

Start in a disposable Git project until you are comfortable with approvals.

Before you start#

PacketCode is installed and on PATH.
The current directory is a Git repository you can safely change.
You have a provider credential, a Codex CLI sign-in, or a running Ollama service.

Configure and start#

packetcode

First-run setup asks for a provider, model and credential when required. It writes the user configuration under the PacketCode data home.

For the first prompt, ask PacketCode to inspect the project and propose a small change without editing. Review the files it reads and the plan it returns. Then request the change and approve only the exact file operation or command you understand.

Verify#

Exit the interface and inspect the repository:

git status --short
git diff --check
git diff

Run the project's own test command. Resume PacketCode and confirm the prior conversation is available before doing further work.

If first-run setup selected the wrong provider, update ~/.packetcode/config.toml or the relocated data home described in Configuration.

If it does not work#

Symptom	Check	Recovery
First-run setup fails	Whether it is setup or provider authentication	See First-run setup or provider authentication fails
The first turn produces no edit	Whether an approval was declined	A refused action is the approval boundary working, not a failure
A command did not run	Whether the permission policy allowed it	See A command or edit did not run
A file could not be read	Whether it is on the never-read list	See A file read is refused