Check Current Business Central Sources with Perplexity CLI
Note: This blog is a personal notebook. I write it to record what I work on, for my own reference, not to publish it on social media or to promote myself. If a post is still useful to you, I am glad, but that is not why it exists.
This post was published on August 20, 2026. Software versions, product features, links, and tool availability may have changed since then. Always check official documentation for the latest information. Some screenshots show small details. Zoom in on the page to see them clearly.
A model cannot know about a Business Central change published after its training cutoff. Its knowledge is a printed timetable. Perplexity CLI (pplx) is the live departure board: a coding agent can search public sources while you work on an AL extension.
Problem
Business Central releases, AL tooling, and Microsoft Learn guidance change often. A model’s answer about a recent feature can sound right and still be out of date. A wrong design can then reach code review or a sandbox before anyone finds the error.
Why this matters
Current research gives you the source, the version, and the date behind a claim. It does not make the claim correct. For AL work, use the source to decide what to test. Then compile the code and validate it against your target Business Central version.
Architecture
pplx runs on your development machine, not inside Business Central. Claude Code, GitHub Copilot CLI, and the GitHub Copilot app call it through a shared Agent Skill. Here is how one question moves through the setup:
No step changes an AL object or reaches a Business Central API. The query leaves your machine for Perplexity’s API, so keep customer records, tenant details, credentials, and private source code out of it.
Demo steps
The pplx release supports macOS on Apple Silicon, Linux x86_64, and Linux arm64. It has no native Windows binary. On Windows, run pplx in an approved Linux environment, and check that your agent process can reach it there. CLI installation
-
In your AL workspace in VS Code, open View > Terminal. Read the CLI installer before you run it:
curl -fsSL https://github.com/perplexityai/perplexity-cli/releases/latest/download/install.sh | sh pplx --versionThe installer checks the binary checksum and installs to
~/.local/bin. Ifpplxis not found, add that folder to your shellPATH. -
Get a separate Perplexity API key. Run
pplx auth loginfor interactive setup. For an agent that cannot log in interactively, passPERPLEXITY_API_KEYto the agent process through an approved secret-management method. Never commit the key or paste it into a prompt. Skill authentication guidance -
Test a public-docs search yourself:
pplx search web "Business Central AL API current guidance" \ --domains learn.microsoft.com -n 5Check the JSON output for relevant Microsoft Learn links, and keep private project data out of the query. CLI usage
-
For Claude Code in VS Code, install Anthropic’s Claude Code extension, sign in, and run the plugin’s install commands in its panel:
/plugin marketplace add perplexityai/api-platform-developers /plugin install perplexity-platform@api-platform-developers /reload-pluginsThe plugin bundles more than the pplx-cli skill, so review its contents first. In Plan mode, ask:
/perplexity-platform:pplx-cli Find current Microsoft Learn guidance for this Business Central AL API question. Cite the relevant pages, state the applicable version, and propose a plan. Do not edit files. -
For GitHub Copilot CLI, install only the published skill, not the broader Claude Code plugin:
copilot skill add https://raw.githubusercontent.com/perplexityai/api-platform-developers/main/skills/pplx-cli/SKILL.md copilotIn the session, run
/skills info pplx-clito confirm that it loaded. If the session was already running, run/skills reloadfirst. Then ask:Use the /pplx-cli skill to find current Microsoft Learn guidance for this AL API question. Give source links and a plan; do not edit files.Copilot CLI skills · CLI commands -
In the GitHub Copilot app, skills configured for Copilot CLI or your repositories are available automatically. Check that
pplx-cliappears under Customize > Skills, then ask for a source-backed answer in Plan mode. A listed skill does not prove that the command can run. Confirm that the session can executepplxand reach its stored credentials, especially in a cloud or sandboxed session. GitHub Copilot app skills
What is intentionally simple
The example runs one public-docs search. It does not automate AL edits, query tenant data, or set up CI. You can stop after the terminal test and hand an agent the source links yourself.
Risks and limits
Search results can be old, incomplete, or written for another Business Central version, so open the source page and check its scope. The Perplexity API key is separate from your Claude or GitHub Copilot account. Agent shells, sandbox settings, and environment variables can differ from your terminal, so test the command where the agent runs.
Next iteration
Add one repository instruction for release-sensitive AL questions: check current Microsoft Learn pages, record the target Business Central version, and ask before editing. Keep it only if the team uses it.
Closing note
Live search closes a knowledge gap in the model, not a validation gap in your code. For Business Central work, the final checks stay the same: source review, AL compilation, and sandbox testing.