Skip to main content

Project Agent CLI

Install the client with python -m pip install project-agent-client, or install from this repository with python -m pip install ./apps/cli. Build a wheel with python -m build apps/cli for distribution. The installed entry point is project-agent; do not install it into the same environment as the legacy backend package, which exposes the same command name.

This separately packaged client forwards Task, Query, Sprint and Proposal scene commands, Quest Task handoffs, and explicitly supported Context, Doc Hub, Meeting, Bootstrap, Attribute, Report, Monitoring and Scheduled commands. The service must implement and authorize each operation; this client cannot override a service-side rejection. Scene receipts and the stdout, stderr and exit code of bridged commands are preserved. Administrative database and upgrade operations are not exposed through this client. The server's database location is never selected by a client-supplied path.

Configure PROJECT_CENTER_URL and set MAGIC_CAMPUS_API_KEY to your Magic Campus API Key (access token). You can instead set PROJECT_CENTER_TOKEN to an API Key or existing service grant; a non-empty PROJECT_CENTER_TOKEN takes precedence when both are set. The client sends the selected credential as Authorization: Bearer <token>; it does not need Magic Campus account API settings or service database credentials. HTTPS is required except for a local loopback service. The client does not automatically retry a write because a network failure can leave its outcome unknown. Legacy Doc Hub JSON-file arguments are read on the client and sent as inline JSON; paths are never read on the server. A valid Magic Campus API Key authenticates the caller; the service accepts the actor supplied in the request without requiring it to match the account behind that key. Existing business validation still applies. The key therefore grants access to operations across projects and must be kept within the trusted environment.

Meeting tasks run and tasks resume execute on the service, using the selected actor. Existing plans must resolve to that actor; a resume batch with a plan for another actor is rejected. Task writes use the service-side Quest handoff. Meeting notifications are sent by the service's magic-campus executable, so that executable and its account configuration must be available in the service runtime; an absent executable leaves the notification pending for retry. The meeting-assistant skill uses the same PROJECT_CENTER_URL and PROJECT_CENTER_TOKEN for meeting state when those are set, and does not fall back to a local database if the remote service is unavailable.

For a Magic Campus API Key or a service grant with trustActorRefs: true, the runtime can set PROJECT_CENTER_ACTOR_REF to the current verified actor JSON (e.g. {"userId":"..."}) for CLI bridge operations which need a user. A bound actor credential does not need this variable. Operations that require an active actor continue to apply their existing business checks.

Metadata

Release files for project-agent-client 0.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for project-agent-client 0.1.4
File Size Uploaded Provenance Actions
project_agent_client-0.1.4.tar.gz 23.1 kB Without provenance Details for project_agent_client-0.1.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for project-agent-client 0.1.4
File Interpreter ABI Platform Actions
project_agent_client-0.1.4-py3-none-any.whl Python 3 none any Details for project_agent_client-0.1.4-py3-none-any.whl

Total release size: 42.8 kB

Release files / project_agent_client-0.1.4.tar.gz

Download URL project_agent_client-0.1.4.tar.gz
Size 23.1 kB
Tags Source
SHA-256 checksum
How to use checksums
ec8243e9d2d65719c6d1283be39306abff915ca1222168f0c01f97fbc71aebf4
BLAKE2b-256 checksum
How to use checksums
a145cd50cf78c9e97200435847cc1e1b0c34a3c62e85d13be2ef10bcaa732606
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.12

Release files / project_agent_client-0.1.4-py3-none-any.whl

Download URL project_agent_client-0.1.4-py3-none-any.whl
Size 19.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8ac4871cce85503a844de3742fe83bad58a4f23472209a1941b11dd6a6c2fb3a
BLAKE2b-256 checksum
How to use checksums
d3efa2af419b13f5927f8df65ca34db7cf9d41d5c58abfecdbfd03d4fef55435
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.12

Security for project-agent-client 0.1.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page