initialize_project
Prepare a newly-connected project: clone the repo, detect the stack, and
stand up its sandbox.
Moves a project from PENDING_INITIALIZATION toward READY. Runs in the
background and returns immediately - poll get_project and read
status_data.status until it is READY (that’s when the project gains the
workspace_id that start_task and the setup tools need). Safe to call again
(no-op if the project is already prepared). Requires an admin-level user.
UUID
required
Project UUID (from list_projects).
UUID
Workspace UUID if the project already has one; omit for a fresh project.
rerun_initialization
Rerun a failed / needs-action initialization step.
Use when a project’s status_data.status is ERROR or NEEDS_ACTION after you
have fixed the cause (e.g. set the right install command via
update_setup_config). Requires an admin-level user.
UUID
required
Project UUID.
UUID
required
From list_projects → status_data.initialization_job_id.
UUID
Workspace UUID, if the project has one.
list_projects
Read-only
List the Autonomy projects visible to the authenticated user.
Returns projects grouped by organization, trimmed to the fields the tools
actually take (ids, names, status, workspaces). Use this to discover the
project_id and its workspace_id needed by the task tools.
To re-check one project’s readiness afterwards, poll get_project - this
listing re-sends every project in the org on each call.
string
Optional filter, e.g. ‘READY’ to show only ready projects.
get_project
Read-only
Get one project’s data, including its initialization/readiness state.
Cheaper than list_projects when you already have the id - and the right way
to re-check a single project’s status while polling after
initialize_project.
Unlike the listing, this errors rather than returning nothing when the
project isn’t visible to you: a not-found while polling a just-connected
project means “not visible yet”, not “gone” - keep polling. (Members only
see READY projects on this read; admins see every status, which is why the
initialize_project flow, admin-only itself, never hits this.)
UUID
required
Project UUID.
UUID
Workspace UUID, if the project has one.
list_available_projects
Read-only
List every project row in the org, linked or not.
These are the projects you can add with add_projects. A repo appears here
only once the org’s git app has synced it, so one the app was never granted
won’t be listed (install the Autonomy GitHub App on it first). Requires an
admin-level user.
is_linked tells you which are already in the org’s active set.
No parameters.
add_projects
Add projects to the org’s active set (link them for use).
Merges the given ids into the currently-linked set (FEI’s underlying call
replaces the whole set, so the current links are read first and preserved).
Use remove_projects to unlink. After adding a fresh project, run
initialize_project to stand up its sandbox.
array
required
Project UUIDs (from list_available_projects) to link. These are ADDED to the org’s linked set - already-linked projects stay linked. Requires an admin-level user.
remove_projects
Unlink projects from the org’s active set.
Reads the current links and re-links everything except the given ids -
an explicit, targeted unlink (the safe counterpart of add_projects).
array
required
Project UUIDs to UNLINK from the org’s active set. Only these are removed; every other linked project stays. Requires an admin-level user.