ph tara
Tara resources: login, search, info, add, remove, install, list, outdated, upgrade, publish
This page is generated from
ph tara --helpbynpm run geninsite/, so do not edit it by hand.
text
Usage: ph tara <command>Account
login
text
login [--org <slug>] [--sso <org>] [--url <address>] [--no-browser]
Log in with the browser (GitHub, GitLab, SSO): a short-lived session for privileged work, plus
a personal token for daily work. Both belong to ONE organization: --org picks it; with several
organizations and no --org you choose from a list (without a terminal, --org is required).
--no-browser: only print the address to open on another machinelogin (2)
text
login --token-stdin Log in with a personal token (CI, machines without a browser); its organization is learned from Taralogout
text
logout Revoke the sessions, remove sessions and tokens of every organization from this machinewhoami
text
whoami [--json] Account, current organization and role, session expiry
(ph org, ph project Organizations, members, invitations, projects: ph org --help)tokens
text
tokens [create <name> | revoke <id>] My personal tokens (creating a token needs a session)keys
text
keys [trust <key> | remove <keyId>] Tara public keys used to verify package signaturesLearn
search
text
search [keyword] [--kind <kind>] [--channel official|org|user|community] [--mine] [--json]
Find resources (kind: skill, agent, kit, prompt, harness). All channels by default;
--mine: my personal resources, including private ones. Names are <owner>/<name>:
aiforge/…, an organization (acme/…) or a person (an/…)info
text
info <name> Resource details and versionsread
text
read <name>[@version] [file] README (default), CHANGELOG.md or a file in the packagedocs
text
docs <name>[@version] [kind|number] [-o file] Bundled docs: install guide, usage guide... (text is printed, PDF is saved to a file)diff
text
diff <name> <old version> <new version> Compare two versionsstats
text
stats <name> [--days 30] Downloads per day and per version; sessions used, cost (Ryoma)Use in a project (recorded in phillip.lock, commit it so the whole team installs the same thing)
add
text
add <name>[@constraint]... [--yes] Add a resource, resolve dependencies, pin the version and install. A bare name means aiforge/<name>,
then your current organization, then your own personal store (never someone else's: use the full
<owner>/<name>). A community resource (public, from another owner, not reviewed) needs confirmation: [y/N] prompt in a terminal; with no
terminal (CI) it needs --yes. PHILLIP_TARA_COMMUNITY=deny: block entirelyremove
text
remove <name>... Remove a resource from the projectinstall
text
install Install the exact versions in phillip.lock (fresh clone on a new machine)list
text
list [--json] Pinned resources and versions, with a warning for yanked versionsoutdated
text
outdated [--json] Resources with a newer versionupgrade
text
upgrade [--latest [name...]] Move to the newest version within the constraint; --latest: relax the constraint
(ph init <harness> Apply a harness to the project)Contribute (three layers: personal -> organization -> public; only aiforge/ has a review)
new
text
new <kind> <name> [--org <org> | --personal] [--description ...] [--owner <email>]
Create a new resource from a Tara template. --personal (default when your role in the
organization cannot publish): your personal storecheck
text
check <directory> [--org <slug>] Run Tara's checks (saves nothing)publish
text
publish <directory> [--org <slug>] [--visibility private|internal|public]
Publish a version. Default: your personal store (an/<name>, private); --org <slug>: that
organization (acme/<name>, internal; allowed by its publish policy, never for viewers).
Passing the automatic scan is enough: it is released immediately, no reviewcontribute
text
contribute <name> --org <slug> [--json] Copy a personal resource to an organization (records you and the source, no review)import
text
import <source> [--to <org>|--personal] [--only a,b] [--yes] [--json]
Import plugins, skills, agents and commands from a GitHub or GitLab repository (URL, or GitHub owner/repo[@ref][/folder]):
Tara scans it at a pinned commit, every item goes through the automatic scan, source and license are
recorded. Default target: your personal storevisibility
text
visibility <name> <private|internal|public>
Personal: private or public; organization: internal or public (owner or admin).
Public means the community rules (no executable components, scan, model review)report
text
report <name> --reason ... Report a resource (suspected malware, deception, data leak); Tara rescans right awaysubmissions
text
submissions My submissions and their statusstatus
text
status <name>@<version> State, check results, reason for being sent backpull
text
pull <name>[@version] [--dir ...] Get the source of a version to editbump
text
bump <directory> <version> --changelog ... Set a new version and a CHANGELOG entryVersion lifecycle
deprecate
text
deprecate | undeprecate <name>@<version> [--reason ...]yank
text
yank <name>@<version> --reason ... Yank a seriously broken version
(the owner of a personal resource, or an organization owner or admin, can do this without a session)text
Review of the official catalog aiforge/ and user reports moved to the admin console (admin.<your domain>, platform staff with the moderator or
super_admin role). review, approve, request-changes and reports only print where to go. Versions of aiforge/
resources are deprecated, restored and yanked there too.Admin (organization owner or admin, needs a session; people and roles: ph org members, ph org invites)
audit
text
audit [--since <7d|2026-10-01>] [--until ...] [--actor <login>] [--action <version|version.yank|...>]
[--resource <name>] [--org <slug>] [--limit 50] [--json]
Log of state, role and notification channel changes of the current
organization (owner or admin; contains no secrets)audit (2)
text
audit --export --from <YYYY-MM-DD> --to <YYYY-MM-DD> [--format csv|json] -o <file>
Export the log of a date range (UTC, both days included; the plan limits how far back: Free 90
days, Team 1 year, Enterprise 3 years). Tara signs it with Ed25519; Phillip checks the signature
with the public key from /v1/signing-keys (or a key pinned with ph tara keys trust), prints
"Signature valid" and only then saves <file> and <file>.signotify
text
notify [list] [--org <slug>] [--json] Notification channels per organization (via the notify plugin on Tara)notify set
text
notify set <org> <plugin> [--set name=value]... [--events a,b] [--disable]
Set a channel: the plugin is a kit pinned on the server (kit-notify-telegram...),
--set is plugin-specific config (chatId...; do not enter tokens, secrets live on the server),
--events: submission.pending, submission.approved, submission.returned,
version.published, version.yanked (empty: all events)notify test
text
notify test | remove <org> <plugin> Send a test | remove the channelOther
announcements
text
announcements [--json] Active announcements from PhillipCLI for the current organization. Warnings and critical ones are also
printed (stderr) by other ph tara commands, once per 24 hours each (PHILLIP_NO_ANNOUNCEMENTS=1: off)auth-header
text
auth-header Print the auth header for Claude Code (headersHelper)text
Tara address: PHILLIP_TARA_URL, or save it with ph tara login --url. Token: PHILLIP_TARA_TOKEN (CI) or the machine's secret store,
one per organization. Organization: PHILLIP_ORG (CI) or the one saved by ph tara login / ph org switch.