loomster

Run awslabs/loom on your laptop or your AWS account from one repo, on chant, with one command per tier.

Run Loom locally Go to production View on GitHub

Loom is AWS Labs’ application for building, deploying and governing agents on Bedrock AgentCore. loomster deploys Loom v1.9.0 as six CloudFormation stacks written in chant, in three tiers, with the backup, restore, upgrade, rotation and drift Ops to run it.

Coming from

Loom's SAM deploy Your make targets and environment.sh settings, mapped.

CDK, SAM or CloudFormation Stacks, synth, deploy and cross-stack references, in chant.

Terraform, Terragrunt or Pulumi Modules, plans and state, and what changes without a state file.

The AgentCore starter toolkit What Loom adds around your agents, and where they fit.

Nothing yet Start with Loom on your laptop.

Your setup

I'm evaluating for my org

I review security

I run the platform

I'm on call

I work with a coding agent

I want to try it

Status

Every tier deploys end to end on Floci and on a real AWS account, and Loom’s own API has deployed an agent to READY as loomster’s backend role.

Tier	Floci	Real AWS
`light`	all stacks, local app with a real login	deployed, served, an agent deployed through Loom’s API
`production`	all stacks and tier resources	all stacks over HTTPS, assistant `READY`, screens validated through MFA Cognito
`production-ha`	all stacks, Multi-AZ requested	all stacks, Multi-AZ and rotation live, beside a second instance

Validation has the details, the recorded claims, and what no run has shown.

Hand the setup to your agent

Run Loom locally has the same steps by hand. Or paste this into your coding agent in a clone of the repository. It brings Loom up on your laptop and never touches an AWS account (Drive loomster with an agent).

Set up loomster with your coding agentThe steps work by hand too.

Show the prompt

Set up loomster in this checkout and bring Loom up locally.
Read https://intentius.io/loomster/llms.txt first, then
https://intentius.io/loomster/getting-started/ and follow it.
Report the URL and the login it prints, and the result of `just validate`.
Never run `chant approve` or `just grant`, never deploy to or delete from a real AWS account unless the person asked for that in this session, never register an identity provider in Loom, and never push or edit the `chant/lifecycle` branch.