[immakermatty]

Status: ready for review. Lazurio's build of the Composio CLI. Plan: HumanAndMachine-ai Mission Control DEV-6626.

Why

Lazurio's Launchpad has to find a person's default Composio organization, the one Composio creates when the account signs up, and make it current in the person's personal Environment. Otherwise Composio's browser sign-in lands in whichever organization is open in Composio's web dashboard.

The default organization is the account's oldest. GET /api/v3.1/org/list lists organizations newest first and marks none as the default, so created_at, which the API returns with every organization, is the only reliable way to tell. The CLI drops it: listOrganizations keeps only id and name, and composio orgs list prints [{id, name, is_selected_global_org}].

What changes

• composio orgs list prints [{id, name, created_at, is_selected_global_org}] on a piped stdout. created_at is the API's string, unchanged (an ISO 8601 date-time).
• listOrganizations returns OrganizationListItem, an OrganizationSummary plus created_at, taken from the typed @composio/client response, which already declares it as a required string.
• Tests:
  • the client test gives each organization its own created_at and updated_at and expects exactly id, name and created_at;
  • a new orgs list command test expects both organizations' created_at on stdout, the selected marker unchanged, and the unchanged human-readable list on stderr;
  • the test layer's mock org.list now keeps an organization's own created_at (the default is still TIMESTAMP) instead of overwriting it.
• CHANGELOG gets a patch entry under Unreleased, and LAZURIO.md lists this as the fourth difference from upstream (Release source becomes item 5).

What does not change

• id, name and is_selected_global_org, their meaning, and the order of the organizations (the API's).
• The human-readable lines on stderr.
• OrganizationSummary stays {id, name}. The organization pickers of composio login and composio orgs switch, which also build a summary from an explicit org ID, compile and behave as before, and composio login --poll and orgs switch print the same JSON as before.
• No other field of the API's organization, such as updated_at, is added.

Verification

• Without the source change, the two tests fail only on the missing created_at; with it they pass. Focused run (pnpm exec vitest run on the orgs list, client, test-layer, login and orgs switch test files): 45/45.
• pnpm typecheck at the root: 14/14 tasks, including the CLI's src and test typecheck.
• pnpm test in ts/packages/cli: 135 files, 1431 passed, 1 skipped; the skill and lint-boundary validations pass.
• pnpm lint at the root exits 0 with no findings in the changed files (its 50 warnings are all in untouched files). prettier --check on all seven changed files is clean.
• Upstream next (d8f820480664) still prints only the other three fields (formatOrganizationsJson in ts/packages/cli/src/commands/orgs/list/orgs.list.format.ts); no upstream issue or pull request covers it.
• Nothing ran against a real Composio account. The response shape comes from the typed client (@composio/client 2.0.0-rc.11) and the v3.1 OpenAPI, where created_at is a required string.

After merge

Release @composio/cli@0.4.3-lazurio.3 with the "Lazurio CLI Release" workflow. That is a Release and needs Matěj's go. Lazurio/LazurioPlatform then bumps its pinned build (installer commit and per-target SHA-256). Proposing the change upstream is Matěj's call; upstream next has since moved orgs list into orgs/list/, so it would be a small port.

🤖 Generated with Claude Code

[agentrozjedemeai]

Reviewed exact head c3e8611 against e52fc87. The change carries the API-created timestamp through the typed organization list and adds it only to the JSON output; the human-readable output and organization selection behavior remain unchanged. The API client contract declares created_at as a string. In an isolated clone, the CLI suite passed (1431 passed, 1 skipped), CLI typecheck passed, and oxlint/prettier passed for changed files. Head CI checks passed; no open threads or competing review requests. Non-blocking downstream note: orgs list defaults to 50 entries, so a future consumer selecting the oldest org should handle pagination if accounts can exceed that limit. No merge or release performed.