Use a B4 agent
A B4 connection points to an agent route on a server. That server owns its model configuration and workspace. It can run locally on your Mac or at a compatible remote HTTPS endpoint.
Start with NavlogCopy link to section: Start with Navlog
Navlog is the maintained B4 example. It prepares a flight plan using weather tools, reference material, and computed results. You can first inspect a recorded aircraft lookup to see a request, tool call, and result without configuring a server.
When you are ready to run it, read the Navlog guide for setup and requirements.
The example needs its own model-provider configuration. Signing in to Codex or Claude Code does not provide the B4 server with a model credential.
Connect an existing serverCopy link to section: Connect an existing server
Start the example server using its guide. In b4app, open Settings → Connections, use the add control, and choose B4 agent…. Enter the server address and the exact agent route reported by that server.
A local address can use loopback HTTP. A remote endpoint must use HTTPS. If it requires an API key, use the connection form's credential field rather than putting the key in a URL or conversation.
Check that the connection is available before starting a conversation. The app supports compatible agent routes; do not assume every workflow or graph endpoint is interchangeable with an agent.
Let the Mac manage a local projectCopy link to section: Let the Mac manage a local project
Under Settings → B4 projects, choose Attach B4 project… and select the trusted project directory. It needs its B4 configuration and installed project CLI. Configure the environment file if the project needs one, start the server, then connect a discovered agent route.
Registration inspects project code. Only attach a project you trust. The app distinguishes a server it starts from one you started independently; attaching an endpoint does not give it ownership of that process.
Follow a turnCopy link to section: Follow a turn
Start with a read-only request that you can compare with the recorded lesson:
Read aircraft/c172n.md and tell me the aircraft model, usable fuel, and configured cruise RPM. Cite the file. Do not change any files, fetch weather, or file a flight plan.
Follow readDoc and compare its result with the response. The file in your checkout may differ from the pinned revision in the recording, so check the source you are actually running.
Once that works, follow the framework guide for a planning task. A weather result is tied to its observation time. The example demonstrates agent behavior and is not qualified for operational flight planning.
If you ask the example to record a flight plan, it requires approval. Its tool writes a local record and reports that it was not transmitted. An approval and a local file are not evidence of an external filing.
To learn how the agent is built, continue with the framework flight-planner guide.