
Security News
pnpm 11.5 Adds Support for Recognizing npm Staged Publishes
pnpm 11.5 now recognizes npm staged publish approvals in release metadata, preventing those releases from being mistaken for lower-trust package publishes.
@loopstack/accessing-tool-results-example-workflow
Advanced tools
A simple workflow showing different methods of how to access tool results in a subsequent workflow step.
A module for the Loopstack AI automation framework.
This module provides an example workflow demonstrating how to store and access data across workflow transitions using typed workflow state.
The workflow shows how to persist data between transitions by returning updated state from transition methods. Understanding this pattern is essential for building workflows that pass data between steps. For example, storing tool results in one transition and reading them in the next.
By using this workflow as a reference, you'll learn how to:
state parameterMessageDocument and DocumentStoreThis example is useful for developers learning to build data-driven workflows that need to pass information between steps.
See SETUP.md for installation and setup instructions.
State is defined as a TypeScript interface and passed to each transition method. Return the updated state from a transition to persist it for subsequent steps:
interface ToolResultsState {
storedMessage?: string;
}
@Workflow({
uiConfig: __dirname + '/workflow-tool-results.ui.yaml',
})
export class WorkflowToolResultsWorkflow extends BaseWorkflow<Record<string, unknown>, ToolResultsState> {
constructor(@Inject(DOCUMENT_STORE) private readonly documentStore: DocumentStore) {
super();
}
}
In the initial transition, save a message document and return updated state:
@Transition({ to: 'data_created' })
async createSomeData(
ctx: WorkflowContext,
args: Record<string, unknown>,
state: ToolResultsState,
): Promise<ToolResultsState> {
await this.documentStore.save(MessageDocument, {
role: 'assistant',
content: `Stored in initial transition: Hello World.`,
});
return { ...state, storedMessage: 'Hello World.' };
}
The returned state is persisted automatically and available in later transitions.
In a subsequent transition, read values from the state parameter:
@Transition({ from: 'data_created', to: 'end' })
async accessData(ctx: WorkflowContext, state: ToolResultsState): Promise<unknown> {
await this.documentStore.save(MessageDocument, {
role: 'assistant',
content: `Accessed from previous transition: ${state.storedMessage}`,
});
return {};
}
import { Inject } from '@nestjs/common';
import { BaseWorkflow, DOCUMENT_STORE, Final, Initial, MessageDocument, Workflow } from '@loopstack/common';
import type { DocumentStore, WorkflowContext } from '@loopstack/common';
interface ToolResultsState {
storedMessage?: string;
}
@Workflow({
uiConfig: __dirname + '/workflow-tool-results.ui.yaml',
})
export class WorkflowToolResultsWorkflow extends BaseWorkflow<Record<string, unknown>, ToolResultsState> {
constructor(@Inject(DOCUMENT_STORE) private readonly documentStore: DocumentStore) {
super();
}
@Transition({ to: 'data_created' })
async createSomeData(
ctx: WorkflowContext,
args: Record<string, unknown>,
state: ToolResultsState,
): Promise<ToolResultsState> {
await this.documentStore.save(MessageDocument, {
role: 'assistant',
content: `Stored in initial transition: Hello World.`,
});
return { ...state, storedMessage: 'Hello World.' };
}
@Transition({ from: 'data_created', to: 'end' })
async accessData(ctx: WorkflowContext, state: ToolResultsState): Promise<unknown> {
await this.documentStore.save(MessageDocument, {
role: 'assistant',
content: `Accessed from previous transition: ${state.storedMessage}`,
});
return {};
}
}
This workflow uses the following Loopstack modules:
@loopstack/common — Base classes, decorators, DocumentStore, and MessageDocumentAuthor: Jakob Klippel
License: MIT
FAQs
A simple workflow showing different methods of how to access tool results in a subsequent workflow step.
The npm package @loopstack/accessing-tool-results-example-workflow receives a total of 38 weekly downloads. As such, @loopstack/accessing-tool-results-example-workflow popularity was classified as not popular.
We found that @loopstack/accessing-tool-results-example-workflow demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
pnpm 11.5 now recognizes npm staged publish approvals in release metadata, preventing those releases from being mistaken for lower-trust package publishes.

Security News
Federal audit finds NIST lacked a plan to clear the NVD backlog, wasted funds on duplicate work, and delayed use of CISA data.

Research
/Security News
A mini Shai-Hulud campaign compromised Red Hat Cloud Services npm packages to steal developer and CI/CD secrets during installation.