Loading…

Delivery Loop

Sign in to your delivery workspace

πŸš€ Guided setup

New project

Delivery Loop control panel

πŸ“‹ Stories
πŸ’¬ Assistant
πŸ“ Feedback
πŸ€– Agent
βš™ Setup

πŸ›‘ Admin console

Platform operations across every organization β€” analytics, users, structure, and support. Distinct from the user app, which is about a single customer's delivery.

πŸ“Š Analytics
β€”
πŸ‘₯ Users & access
πŸ’³ Plans & billing
β€”
πŸ€– Agent runtime
β€”

Runs agent sessions on your Claude subscription (flat-rate). Stored as CLAUDE_CODE_OAUTH_TOKEN. Once the token + Cloud Run job are set, β–Ά Work this runs entirely in-site.

πŸ— Structure & defaults
πŸ›Ÿ Support
Per-user activity & access β€” help customers get unblocked.

πŸ’¬ Assistant β€” all

Chat about this project and I turn what we discuss into scored, estimated stories in its backlog β€” then we refine and align them together. Share an idea, paste documentation, or upload a doc for context below. I can also act: pull feedback, sync the dashboard, find/answer/prioritize work.

Paste documentation, a transcript, requirements, or a list of items β€” or upload a text document. The AI extracts scored, estimated stories into this project's backlog (skips anything already built).

πŸ“ Share an idea

Describe what you'd like or what's not working. I'll ask a couple of quick questions, then log it in Azure as a scored, time-estimated story β€” recorded for review. No technical detail needed.

πŸ”— Shareable feedback link

Give non-technical people a link to chat their ideas straight into this project β€” no account needed.

β€”

πŸ€– Agent

Claude Code working on this project β€” see if it's active, and guide it with replies.

How your agent works & how to steer it
What it does

Given only your token, a coding agent pulls Ready stories through our API, builds them, moves each Active β†’ Resolved (auto-timed), and posts questions and notable decisions back on the story. It all streams into the live activity feed on Setup.

How you steer it
  • Standing guidelines (build cadence, conventions, deploy/test) β†’ Setup β–Έ AI ledger β€” fed to the agent via config.json.
  • Answer its questions β†’ Stories (the Pending queue) or Needs you.
  • Nudge a live session β€” reply in its terminal below (e.g. β€œpush”, β€œcontinue to the next Ready story”).
β€” add it to the repo so the agent knows how to build, verify & run it.
βœ… Ready to work β€” fetch a story into the terminal
Select a project to see its Ready queue.
Session history

Users

Invite people into your account by email and share an org β€” or just specific projects β€” with them. A project invite adds them to that org with access to those projects only.

Loading…

Organizations

An org holds the master credentials (Azure DevOps PAT + OpenAI key) its projects share.

Add an organization

You only need an Azure DevOps PAT (Work Items: read/write) to start β€” the AI runs on our platform LLM out of the box. Add your own OpenAI/Anthropic key any time to use your preferred model and lift the free monthly limit. Storage is only needed for feedback sources.

πŸ”‘ Credentials
Bring your own key for unlimited AI on your chosen model. Leave blank to use ours β€” capped monthly on the free plan.
Lets the loop push design assets and β€œwire-up” PRs into your product repos. Skip if you’re not connecting GitHub.
Run different models across different projects from one hub β€” set the default here, override per project.

πŸ“Š Dashboard

Delivery over time β€” hours, throughput, estimates vs actuals.

Loading…

Delivery overview

β€”

✦ Needs your input

Work through the open questions across your projects β€” answer, assign, or skip.

Checking…

New project

Basics
Set it and the dashboard's Executive Summary opens with your exact words; leave blank and the AI infers one from the roadmap.
Keys (org master vs project-specific)

Use org master = this project shares its org's PAT/OpenAI/storage. Project-specific = its own keys (e.g. an isolated OpenAI key for separate spend). Store the key values under Credentials or on the org.

Estimation & cost
Structure & style (per project β€” all configurable)

Leave blank for the standard defaults. These drive bootstrap so each org/project can have its own structure.

πŸ”Œ Connections

Connect sources one at a time β€” only what you use. βœ“ connected Β· β—‹ not yet.

πŸ”· Azure DevOps β€” required
βœ“ via org keys
β—‹ πŸ™ GitHub β€” wire-up PRs
β–Ύ

The GitHub token lives on the org. This sets the repo for asset/wire-up PRs.

β—‹ πŸ“¦ Docs store β€” blob container (needed for Teams/email/docs)
β–Ύ
β—‹ πŸ’¬ Teams channel Β· setup & access β†—
β–Ύ
Reads channel messages read-only (app-only, no sign-in) and turns them into stories. Needs a one-time Entra app + admin consent β€” see setup & access β†—. Paste the app's tenant + client IDs below; the client secret goes in org keys as TEAMS_CLIENT_SECRET.
In Teams: β‹― next to a channel β†’ Get link to channel. Or add one, then Browse to pick more from the team. Feedback is tagged by channel name.
β—‹ πŸ“§ Support email
β–Ύ

Reads a shared support inbox (Graph Mail.Read, reuses the Teams app) β†’ stories. Set up email access β†—

Senders reach this project by putting its subject term above in the email β€” that's the project link. Unless public, only project members' emails become stories.

β—‹ πŸ”” Notify
β–Ύ

πŸ“‹ Stories

Every story in this project. The Pending queue is what needs your review β€” set a priority (P1–P4) on each card, or open one to answer its questions and move it to Ready.

Loading…

Run the loop β€” no project selected

Each action runs against the selected project with its org's keys, and shows live output below.

output appears here…

πŸ‘€ My profile

Your personal settings β€” separate from an org's shared keys. These identify you when the tool acts on your behalf.

πŸ”· My Azure DevOps PAT β€” so your work is credited to you

Add your own PAT per org. Then anything you do (answers, comments, claiming a story) is attributed to you in Azure DevOps and can be assigned to you β€” instead of the shared org identity. Required for members to act on a shared org's project. how to get one β†—

β€”
πŸ™ My GitHub access

A personal GitHub token (scope: repo) tied to you β€” used when the tool opens PRs or connects repos on your behalf. how to get one β†—

Connections & keys

Plug in a key to unlock each connection. You only need Azure DevOps and OpenAI to start β€” add the rest whenever you want what they unlock.

🏒 Org keys β€” shared across all projects

Azure DevOps & Teams live at the org level β€” set once, every project uses them.

β€”
πŸ“ Project keys
Pick a project.
πŸ”‘ All keys (paste .env / advanced)

Quickest: paste your whole .env β€” every line is saved.

Saved keys
🀝 Access tokens β€” let an agent set things up for you

Create a token so a coding agent can sign in and onboard repos on your behalf β€” no password shared. It runs connect.py with it.

β€”
πŸ™ GitHub accounts

Add one with gh auth login in a terminal, or save a GITHUB_TOKEN above (that's what powers πŸ”— Auto-connect).

πŸ’³ Plan & usage
β€”
Answer
βž• Add an item to

Drop in an idea, notes, or a document β€” we turn it into scored, estimated stories in this project's backlog. No connected source needed.

Text documents (.txt, .md, .csv, .json, .log) are read here and added above. For richer/binary docs or ongoing intake, connect a feedback source (Teams, email, store).

βž• Add a story to

Straight onto the board β€” no AI. Use this when you already know the work.

πŸ‘₯ Invite a user
Pick an org…
πŸ”‘ Your private key