Breeze
for LuumenAI
Read Breeze projects and cards for context, then file the work as an approved step.
Connect Breeze and the agent can see how work is actually tracked: active projects, the cards in each one, who is on the team, and which stage a task sits in. When something needs to be written down — a follow-up card from an incident, a new stage, a person added to a project — the agent shows the change first and waits for your approval. Authentication is by API key.
The Breeze toolbox
18 tools: 7 read, 11 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet CardRetrieve detailed info for a specific card (task) in a project.
- ReadGET_CARDSGet all cards (tasks) for a specific project.
- ReadGet ProjectGet a specific project by ID.
- ReadGet Project PeopleGet all users in a project.
- ReadGet ProjectsRetrieves a list of all active (non-archived) projects in Breeze.
- ReadGet WorkspaceGet a specific workspace by ID.
- ReadGet WorkspacesGet all workspaces.
- WriteAdd Project PeopleAdd people to a Breeze project by inviting them via email. Approval by default
- WriteArchive ProjectArchive a specific project. Approval by default
- WriteCreate CardCreate a new card in a project. Approval by default
- WriteCREATE_LISTCreate a new list (stage) in a Breeze project. Approval by default
- WriteCreate ProjectCreates a new project in Breeze project management system. Approval by default
- WriteCreate WorkspaceCreate a new workspace. Approval by default
- WriteDelete CardDelete a specific card (task) by its ID. Approval by default
- WriteDelete ProjectDelete a specific project by ID. Approval by default
- WriteDelete Person from ProjectDelete a person from a project by user ID. Approval by default
- WriteDelete WorkspaceDelete a specific workspace by ID. Approval by default
- WriteMove CardMove a card to a different stage or position. Approval by default
One prompt, start to finish
What a governed Breeze run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add project people, archive project, create card, create_list, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Breeze — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Put Breeze to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.