Skip to content

Contact ​

Before you ask anyone, check the Frequently asked questions and Troubleshooting. If you're still stuck, this page points you to the right person and the right channel.

Ask someone near you ​

Your own organization answers most day-to-day questions fastest. Start with your organization's Owner or Admin. They handle questions about how to use the tools, your project's process, invitations, roles, and seats. Your project admin handles the project's Guardrails and members. If you don't know who the Owners and Admins are, open the organization's members page in the Portal or run ph org members. Questions about the service itself, such as sign-in problems or an incident, go to PhillipCLI support through the channel your organization was given.

Report a bug ​

When you hit a bug in Phillip, Tara, Bandum, or Ryoma, create an issue on your organization's issue tracker, in that component's repository. If you don't know which repository, ask your organization's Owner or Admin to forward it. A good bug report says what you were trying to do and which command you ran, what happened, and what you expected. It also includes the output of ph --version and ph forge doctor, and the relevant log: ph bandum ui logs if you use Bandum on your machine, or the Phillip Output channel in VS Code.

Mask sensitive information

Don't paste passwords, tokens, or real customer data into an issue or a message. Mask them before you send.

Don't post security bugs publicly. Report them directly to your organization's security team. See Security. If you suspect a resource on Tara contains malicious code or leaks data, use ph tara report <name> --reason "...". Tara rescans it right away, and your organization's Admin, or PhillipCLI platform staff for the official store, handles it.

For a Guardrails false positive, you don't need to create an issue. Send feedback with ph guardrails feedback. See When Guardrails blocks you.

Suggest a feature ​

Create an issue on the same issue tracker and describe the problem you're facing, not only the solution you want. If you want a new skill, agent, or harness, the fastest way is to contribute it yourself. See Get started for contributors. The published plan is in the Roadmap.

If you suspect a service is having an incident, check the Status page before you report.