[immakermatty]

Status: ready for review. The CLI build this needs is released: @composio/cli@0.4.3-lazurio.3 from Lazurio/composio#4 (merged 2026-10-26 on Matěj's go, Pablo approved), and this PR pins it.

Why

On 2026-10-26 Matěj found that his personal Environment showed the Composio apps of a work organization where his personal ones belong.

• Cause. Composio's browser sign-in lands in the organization that is open in Composio's web dashboard. That is often an Organization's one, because people create those there (F42, addendum (2) of 2026-10-13, point 5). The Launchpad then left a personal Environment's organization to the person, because the CLI did not say which organization is the account's default (point 7).
• What the decisions say. Root decision 0162 (its addendum of 2026-10-13, point 2) says the personal Environment uses the account's default organization. Point 7 already named the missing step: "Once the CLI prints when an organization was created, the oldest one can be chosen by the rule."

What changes

• The rule default. A Machine binding whose owner is a person (the personal Environment) gets this rule. The account's default organization is its oldest:
  • Composio's list marks none as the default and lists the newest first.
  • defaultComposioOrganization takes the oldest by created_at.
  • parseComposioOrganizations now keeps createdAt when it is a valid date.
• Brought current the same way as an Organization's organization. The Integrace reading, the sign-in dialog (/api/tools/composio/organizations) and every link and removal (inOwnOrganization) make the default organization current where another one is, journaled as before.
  • The dialog no longer offers a choice there, since the next reading would undo it.
  • The reading reports it as {name, state, default: true}.
  • The page, Začínáme and lazurio integrations list show its name exactly as Composio does, never in an Organization's CamelCase form.
• Nothing is guessed. The default organization is not picked in these cases, and the person's choice stands as today:
  • an organization has no date (Composio's own CLI, or Lazurio's before 0.4.3-lazurio.3);
  • two organizations are equally old;
  • orgs list printed a full page of 50. The CLI prints one page, newest first, so the oldest may be missing (Pablo's note on CLI: orgs list prints each organization's created_at composio#4).
• Docs. F42 gets an addendum of 2026-10-26, and points 1 and 7 of addendum (2) are marked. docs/integrations.md is updated. The preview's fake Composio dates its organizations, with example_user_workspace as the oldest.

What does not change

• An Organization's Environment and a Team Environment still use the organization with the Organization's name.
• A computer: the person still chooses.
• No generated Folder text changes.

The pin: 0.4.3-lazurio.3

• composioBuild names the new build:
  • version and tag;
  • the installer at the release's own commit 5bcde7de8dc78681e8d44262fcf134afab19e091, whose install.sh is byte for byte that of 0.4.3-lazurio.2;
  • the four archives' SHA-256, as the release's checksums.txt lists them and the downloaded archives hash (read 2026-10-26).
• The catalog's target state now names four changes. Tests that pin the build follow, as do docs/integrations.md, environment-tools.md, launchpad-development.md and F42 point 5.
• People update the CLI themselves, as with every pin. An Environment that still has 0.4.3-lazurio.2 keeps the person's choice until they update Composio in Settings → Tools, which says it is not the build Lazurio uses. Older builds print no dates, so the rule falls back to the person's choice, exactly as on main.
• The release itself. Its own installation check passed on Linux and macOS. Its macOS arm64 binary, run in an isolated home with a copy of one real account's sign-in, printed created_at for every organization and gave the default one as the oldest. The isolated home was deleted afterwards.

Verified

• Tests.
  • bun test on the six affected files: 160 pass. The related 44 files after the pin bump: 646 pass.
  • The organization tests now include the default verdict (oldest, tie, undated, empty, full page) and the rule.
  • On a personal Environment: the dialog and the reading make the default organization current after a sign-in that landed elsewhere; an organization switched behind the reading is switched back; a link goes to the default organization; a default that cannot be made current refuses links and is named as Composio names it; an undated CLI leaves the choice to the person.
  • Also covered: date parsing (tests/tools-login.test.ts) and Začínáme's Composio step (tests/first-run.test.ts).
  • bun run check:static passes.
• Browser (headless Chrome against scripts/preview-launchpad.ts, Czech).
  • Personal preview: Composio was signed in to another organization. The dialog's reading switched to example_user_workspace, and Settings → Tools shows "Připojeno jako op@example.com (example_user_workspace)".
  • With "Používají agenti" switched on, Apps → Integrace read it as current. "Aplikace v Composiu" and each app's link lead to …/example_user_workspace/…, with no organization notice and no page errors.
  • Work preview: unchanged, made current in ExampleCompany by the Organization's name.
• Real account. A read-only GET /api/v3.1/org/list on one real account (2026-10-26) confirmed that the API lists the newest first and that the default organization, made at sign-up, is the oldest.

Rollout

After merge: the next Platform release, then Ring 0 (LazurioExampleOrganization) and personal Environments through the pipeline.

Work context

• Agent / thread: Claude Code session 4d869c83-e1c1-41e8-949e-06f1b9dee608 in Matěj's T3 Code thread "ONBOARDING FLOW".
• Machine: matejsuchanek.local.
• Worktree: HumanAndMachine-ai_GEN3/.worktrees/productionspace/LazurioPlatform/DEV-6626-composio-personal-org, branch agent/DEV-6626-composio-personal-org.
• Mission Control: DEV-6626 (HumanAndMachine-ai/mission-control-data:v3, data/mission-control/plans/2026/09/DEV-6626-composio-app-connections.yaml).

🤖 Generated with Claude Code

Note

Use account's default Composio organization for personal Environments

• A personal (non-organization) machine now resolves a new default organization rule: the oldest Composio organization by created_at, used only when the list is complete and has one uniquely oldest valid date; otherwise the current organization stays in force.
• Convergence switches to the default organization when needed; if the default cannot be made current, the Composio reading is closed and integration linking is blocked. The CLI parser now reads and validates created_at on orgs list output (login.ts).
• UI and text surfaces show the default organization's provided name, and a current default renders as connected with no selectable choices.
• Also bumps the pinned Lazurio CLI build from 0.4.3-lazurio.2 to 0.4.3-lazurio.3 with new installer commit and archive hashes (composio-build.ts); all tests and docs updated to match.
• Risk: organization-owned, team, and computer Environments keep their existing rule paths in composioOrganizationRule, but any consumer of ComposioOrganizationRule must handle the new default variant; the pinned build bump changes install/update expectations for every test asserting the old version.

^{Macroscope summarized dd418d1.}

[agentrozjedemeai]

Reviewed exact head dd418d1 for DEV-6626. The personal default-organization convergence, undated/tied/full-page fallbacks, dialog/read/link behavior, and unchanged named Organization path are consistent with the decision. Local focused suite: 147 passed across six files; check:static passed. Release tag and four archive digests match the pin, installer blob matches the prior version; PR CI passed. No blocking findings. Review only; merge remains with Matěj.

[immakermatty]

Published as squash commit bbad4ad on the approved head dd418d1; the squash commit's tree is identical to that head. Afterwards the task worktree and the branch agent/DEV-6626-composio-personal-org were removed, both locally and on GitHub. Nothing from this work remains outside main.

Next step: the fix reaches Environments with the next Platform release. An Environment still on an older Composio build installs 0.4.3-lazurio.3 when the person clicks Update on Composio in Settings → Tools.