AlphaCrew
Menu

Build your crew. Put it to work.

Start with the people on your AI team. Follow one agent through a task, see specialists work together, then see how the work carries on over time.

Configure your team

Give each agent a responsibility, a model and an execution environment. Decide which resources it can use.

Meet Kai. Configure the way he works.

Connections belong to your Host. Each agent chooses a supported model and Image independently; its role and resource access are separate choices.

“Kai will look after stock. I’ll choose OpenAI’s gpt-6.1-sol and the Stock Manager Docker image, then grant access to the inventory exports he needs.”
Configuration brief

Connections belong to your Host. Each agent chooses a supported model and Image independently; its role and resource access are separate choices.

“Kai will look after stock. I’ll choose OpenAI’s gpt-6.1-sol and the Stock Manager Docker image, then grant access to the inventory exports he needs.”
  1. 1Role
  2. 2Model
  3. 3Image
  4. 4Access & crew

  1. You · Team setup

    Give Kai a name

    Agent profile

    Name

    Kai

    Model, Image capabilities and resource grants are separate choices.

    1 / 10

  2. You · Team setup

    Define his responsibility

    Agent profile

    Role

    Stock Manager

    Responsibility

    Investigate stock exceptions and prepare recommendations.

    Model, Image capabilities and resource grants are separate choices.

    2 / 10

  3. You · Team setup

    Choose OpenAI as the provider

    OpenAI → gpt-6.1-sol

    Provider

    OpenAI

    Access

    ChatGPT subscription

    Model, Image capabilities and resource grants are separate choices.

    3 / 10

  4. You · Team setup

    Select gpt-6.1-sol from the connected catalog

    OpenAI → gpt-6.1-sol

    Model

    gpt-6.1-sol

    Ownership

    Saved on Kai; his AI tasks use this model.

    Model, Image capabilities and resource grants are separate choices.

    4 / 10

  5. You · Team setup

    Choose the Stock Manager Docker image

    Execution environment

    Docker image

    Stock Manager

    Model, Image capabilities and resource grants are separate choices.

    5 / 10

  6. You · Team setup

    Review its tools and Skills

    Execution environment

    Tools

    File access and spreadsheet calculations

    Skill

    Office data · guidance loaded when needed

    Model, Image capabilities and resource grants are separate choices.

    6 / 10

  7. You · Team setup

    Set the resource boundary

    Separate grants and profiles

    Resources

    Selected inventory exports; originals preserved

    Model, Image capabilities and resource grants are separate choices.

    7 / 10

  8. You · Team setup

    Save Kai’s configuration

    Separate grants and profiles

    Kai

    Profile, model and Image configured

    Model, Image capabilities and resource grants are separate choices.

    8 / 10

  9. You · Team setup

    Add specialists and a Coordinator

    Separate grants and profiles

    Teammates

    Amy · Emma · Coordinator

    Model, Image capabilities and resource grants are separate choices.

    9 / 10

  10. You · Team setup

    Team configured; no work has started

    Separate grants and profiles

    Configuration

    Each can have a different supported model and Image.

    Your crew

    Kai · Amy · Emma · Coordinator

    Configured · awaiting your assignment

    10 / 10
Example profiles and selections. Stock Manager is the role-facing Docker image label in this illustration. Model availability and resource access follow the configured account and grants.

Illustrative configuration and work records

Define a role

Agent profile

Name
Kai
Role
Stock Manager
Responsibility
Investigate stock exceptions and prepare recommendations.

Choose a model

OpenAI → gpt-6.1-sol

Provider
OpenAI
Access
ChatGPT subscription
Model
gpt-6.1-sol
Ownership
Saved on Kai; his AI tasks use this model.

Choose an Image

Execution environment

Docker image
Stock Manager
Tools
File access and spreadsheet calculations
Skill
Office data · guidance loaded when needed

Set access & build the crew

Separate grants and profiles

Resources
Selected inventory exports; originals preserved
Kai
Profile, model and Image configured
Teammates
Amy · Emma · Coordinator
Configuration
Each can have a different supported model and Image.

Configured · awaiting your assignment

Example profiles and selections. Stock Manager is the role-facing Docker image label in this illustration. Model availability and resource access follow the configured account and grants.

Provider & model

Choose the provider and model for each agent. This example uses OpenAI → gpt-6.1-sol through a ChatGPT subscription connection.

Image & tools

The Stock Manager Docker image shown here describes Kai’s execution environment and default tools. Image capabilities and resource grants remain separate.

Access & future providers

Resource grants remain separate. Direct vendor API Key connections are not integrated yet.

One agent, taking responsibility

Once you set the goal and rules, the agent chooses the next useful step, uses its tools and prepares a result with evidence.

A stock gap. A late delivery. Kai keeps going.

A packaging supplier’s stock manager checks upcoming orders, traces a delayed receipt and finds another warehouse that can cover the gap within your rules.

“Check the next seven days of orders. Investigate shortages, check confirmed receipts, then look for the same SKU in another warehouse. Prepare transfer recommendations that preserve reserved stock and safety levels.”
Task & context

A packaging supplier’s stock manager checks upcoming orders, traces a delayed receipt and finds another warehouse that can cover the gap within your rules.

“Check the next seven days of orders. Investigate shortages, check confirmed receipts, then look for the same SKU in another warehouse. Prepare transfer recommendations that preserve reserved stock and safety levels.”
  1. 1Shortage
  2. 2Receipt
  3. 3Warehouse
  4. 4Rules

  1. Kai · Stock Manager

    Read stock and upcoming orders

    VALVE-01 · Warehouse A

    6,000 on hand − 4,000 reserved = 2,000 available.

    Order SO-204

    3,000 units needed on day 4.

    stock.xlsx + orders.xlsx

    1 / 11

  2. Kai · Stock Manager

    A shortage needs investigation

    Stock + order demand → check confirmed receipts

    1,000 units short

    3,000 needed − 2,000 available = 1,000.

    VALVE-01

    Check confirmed receipts before other warehouses.

    2 / 11

  3. Kai · Stock Manager

    Check the existing purchase order

    Purchase PO-118

    5,000 units · VALVE-01

    Original arrival: day 2 · needed: day 4

    purchases.xlsx + notice.eml

    3 / 11

  4. Kai · Stock Manager

    The receipt is too late

    Purchase order → supplier’s latest notice

    Supplier noticeLate receipt

    “PO-118 is delayed. Expected arrival is now day 6.”

    Needed on day 4; updated arrival day 6.

    Too late for day 4. Check another warehouse.

    4 / 11

  5. Kai · Stock Manager

    Continue to another allowed source

    Late receipt → another warehouse

    Find the same SKU and unit

    VALVE-01 · One-way coffee-bag valve

    warehouses.xlsx

    Kai continues under the standing rules, without waiting for a new instruction.

    5 / 11

  6. Kai · Stock Manager

    Warehouse B has available stock

    Warehouse B · VALVE-01Same SKU and unit

    5,000 on hand − 2,000 reserved = 3,000 available.

    warehouses.xlsx

    6 / 11

  7. Kai · Stock Manager

    Protect reserved stock

    Candidate stock → standing transfer rules

    Same SKU; use unreserved stock onlyPass

    1,000 proposed from 3,000 unreserved units.

    2,000 reserved units stay untouched.

    transfer-rules.csv · no inventory change

    7 / 11

  8. Kai · Stock Manager

    Preserve Warehouse B’s safety stock

    Available after the proposed transferPass

    3,000 − 1,000 = 2,000 units.

    Required safety stock: 1,500.

    Reservations and safety stock are checked separately.

    8 / 11

  9. Kai · Stock Manager

    Check the configured transfer time

    Warehouse B → ATiming checked

    1 day configured transit · needed on day 4.

    Use the configured one-day transfer time; no arrival promise without confirmation.

    9 / 11

  10. Kai · Stock Manager

    Prepare a transfer recommendation

    Rule checks → draft plan with sources

    Draft transfer recommendationDraft only

    1,000 units · Warehouse B → A

    VALVE-01

    Prepare recommendations only. New purchases and customer commitments need the owner.

    10 / 11

  11. Kai · Stock Manager

    Recommendation ready

    Draft transfer recommendationFor review

    1,000 units · Warehouse B → A

    VALVE-01 · source references retained
    Rule checks retained

    B keeps 2,000 available; minimum 1,500.

    1 day configured transit; operational timing unconfirmed.

    Prepared for warehouse review. Inventory records and shipments are unchanged.

    11 / 11
Example file contents and configured rules, compressed into one sequence. Kai follows up a shortage autonomously; the output is a proposed transfer, with timing still subject to operational confirmation.

File-based office workflow · example records and rules

Kai · Stock Manager

Investigates and prepares the recommendation within your standing instructions.

Find the shortage

stock.xlsx + orders.xlsx

Order SO-204 · Day 4

One-way coffee-bag valve

VALVE-01 · Warehouse A

On hand
6,000
Reserved
4,000
Available
2,000
Order needs
3,000

Shortage

1,000 units

Kai continues within your rules

Trace the receipt

purchases.xlsx + notice.eml

Purchase PO-118

5,000 units

VALVE-01

Original arrival: Day 2

“PO-118 is delayed. Expected arrival is now day 6.”

Updated arrival: Day 6

Needed: Day 4

Too late for day 4. Check another warehouse.

Find another source

warehouses.xlsx

Warehouse B

VALVE-01

Same SKU and unit

On hand
5,000
Reserved
2,000
Available
3,000

Available after transfer: 2,000

Required safety stock: 1,500

1 day · needed on day 4

Apply your rules

transfer-rules.csv → draft plan

Standing transfer rules

  1. Same SKU; use unreserved stock only
  2. Leave at least 1,500 available units in B
  3. One-day transfer fits the day-4 need

Draft transfer recommendation

Transfer 1,000 units

Warehouse B → A

Transfer time: 1 day

Source references retained

Recommendation ready

Prepared for warehouse review. Inventory records and shipments are unchanged.

Example file contents and configured rules, compressed into one sequence. Kai follows up a shortage autonomously; the output is a proposed transfer, with timing still subject to operational confirmation.

  1. Find the shortage

    Compare upcoming demand with unreserved stock. Preserve existing allocations and identify the affected order.

  2. Trace the receipt

    Check the confirmed purchase, then read the supplier’s updated arrival notice. Follow the evidence when the original plan no longer covers demand.

  3. Find another source

    Continue to the next allowed option: stock of the same SKU and unit in another warehouse. Separate physical stock from existing reservations.

  4. Apply your rules

    Check reservations, the source warehouse’s safety stock and transfer timing. Deliver a recommendation with its calculations and source references.

Standing transfer rules
  • Check confirmed receipts before other warehouses.
  • Transfer only matching SKU / unit; preserve reservations.
  • Keep B’s available stock at or above 1,500 units.
  • Use the configured one-day transfer time; no arrival promise without confirmation.
  • Prepare recommendations only. New purchases and customer commitments need the owner.

Grounded in AlphaCrew’s file-processing tools and delegated-work design. This website illustration does not run Kai or connect to an ERP. Reading spreadsheets and exported mail, using tools for calculations and preparing artifacts have implementation foundations; this stock scenario is not an end-to-end acceptance claim.

Explore the capability boundaries

A crew, working together

Specialists handle focused assignments. Prepared, independent assignments can run in parallel when Host capacity allows; the Coordinator checks and integrates their results.

Every morning, on your schedule

Your morning, already in focus.

Your specialists summarize personal and team communications, social activity and business data. The Coordinator brings their findings together into your morning briefing.

“Prepare my morning briefing. Let Amy summarize personal and team communications, Emma summarize social updates and Kai summarize stock information. Bring their sourced findings together and highlight decisions for me.”
  1. 1Collect
  2. 2Make sense
  3. 3Deliver

  1. Amy · Personal Assistant

    A specialist hands over a summary

    To the Coordinator

    Personal & team updatesSummary received

    Email, Slack & more

    Specialists report to the Coordinator, with their source references.

    1 / 9

  2. Emma · Social Manager

    A specialist hands over a summary

    To the Coordinator

    Social updatesSummary received

    Facebook, Instagram, X

    Specialists report to the Coordinator, with their source references.

    2 / 9

  3. Kai · Stock Manager

    A specialist hands over a summary

    To the Coordinator

    Stock updatesSummary received

    Business APIs

    Specialists report to the Coordinator, with their source references.

    3 / 9

  4. Coordinator

    Integrate agent summaries

    Amy + Emma + Kai · summaries received

    AmyIntegratedPersonal & team updates
    EmmaReceivedSocial updates
    KaiReceivedStock updates

    Integrating agent summaries

    4 / 9

  5. Coordinator

    Merge related updates

    Amy + Emma + Kai · summaries received

    AmyIntegratedPersonal & team updates
    EmmaIntegratedSocial updates
    KaiReceivedStock updates

    Integrating agent summaries

    5 / 9

  6. Coordinator

    Prioritize what needs you

    Amy + Emma + Kai · summaries received

    AmyIntegratedPersonal & team updates
    EmmaIntegratedSocial updates
    KaiIntegratedStock updates

    Priorities are ready for one shared briefing.

    6 / 9

  7. Coordinator

    Writing your briefing

    Specialist findings → one morning briefing

    Follow up on the launch

    Email and team messages identify a decision for you.

    Email / Slack

    Source links and incomplete reads stay visible.

    7 / 9

  8. Coordinator

    Writing your briefing

    Specialist findings → one morning briefing

    Follow up on the launchEmail / Slack
    Review the campaign response

    Social replies highlight a follow-up for your team.

    Facebook / Instagram / X

    Source links and incomplete reads stay visible.

    8 / 9

  9. Coordinator

    Briefing ready

    Specialist findings → one morning briefing

    Follow up on the launchEmail / Slack
    Review the campaign responseFacebook / Instagram / X
    Check the order change

    An operational update is ready to inspect.

    Business API

    Source links and incomplete reads stay visible.

    9 / 9
Illustrative agent roles and sample content. Specialists pass summaries to the Coordinator; this is not live activity.

Collect

  • Amy

    Personal Assistant

    Email, Slack & more

  • Emma

    Social Manager

    Facebook, Instagram, X

  • Kai

    Stock Manager

    Business APIs

Make sense

AlphaCrew

Coordinator

  • Integrate agent summaries
  • Merge related updates
  • Prioritize what needs you

Deliver

Example output

Morning briefing

Here is what needs your attention today.

  1. Follow up on the launch

    Email and team messages identify a decision for you.

    Email / Slack
  2. Review the campaign response

    Social replies highlight a follow-up for your team.

    Facebook / Instagram / X
  3. Check the order change

    An operational update is ready to inspect.

    Business API

Source links and incomplete reads stay visible.

Illustrative agent roles and sample content. Specialists pass summaries to the Coordinator; this is not live activity.

  1. Collect

    Amy, Emma and Kai each summarize their authorized sources, keeping references and reporting missing or incomplete inputs.

  2. Make sense

    The Coordinator integrates the specialists’ summaries, merges related updates and prioritizes what needs your attention.

  3. Deliver

    Produce one concise briefing with priorities and source references, ready to review at the start of your day.

Choose the sources, reading window and delivery destination. Gmail and Sheets reads have local verification; Slack, social platform reads, additional APIs and the complete scheduled briefing still need configuration and end-to-end verification.

How scheduled work runsSee how the team works

Give each specialist a clear brief

Share the relevant goal, inputs, rules and expected result. Assignment does not add new tools or access. Work assigned to the same agent runs in sequence.

Return results and evidence

Specialists report their outcomes, sources and limitations. The Coordinator receives focused results rather than every private conversation.

Integrate when needed

The Host routes returns so the Coordinator can continue the assignment. Ordinary scheduled success need not wake the Coordinator.

Work that keeps moving

A retained decision can pause an action without losing the work. After a decision, the authorized remainder continues; recurring work returns on its schedule.

A weekly note, through feedback to delivery.

This example retains review before local Markdown delivery. Preparation, the owner’s decision and verified delivery are distinct steps.

“Every Friday, prepare a supplier note from the provided records. Let me review each draft before you deliver it to the selected local publication directory.”
Task & context

This example retains review before local Markdown delivery. Preparation, the owner’s decision and verified delivery are distinct steps.

“Every Friday, prepare a supplier note from the provided records. Let me review each draft before you deliver it to the selected local publication directory.”
  1. 1Start
  2. 2Review
  3. 3Deliver
  4. 4Repeat

  1. Host

    The Host starts the scheduled occurrence

    Schedule → Agent

    Responsibility

    Weekly supplier note

    Trigger

    Friday · configured workspace timezone

    1 / 10

  2. Agent

    The agent prepares a sourced draft

    Schedule → Agent

    Preparation

    Read sources, write and check the draft.

    2 / 10

  3. You · Human review

    Draft v1 is ready for your review

    Owner ↔ Agent

    Draft v1Awaiting review

    Prepared for owner review

    3 / 10

  4. You · Human review

    You request a change

    Owner ↔ Agent

    Your feedbackChanges requested

    “Include the source date for each delivery change.”

    4 / 10

  5. Agent

    The agent revises the same item

    Owner ↔ Agent

    Revision

    The agent adds the requested references.

    The same item is revised; v2 still needs fresh approval.

    5 / 10

  6. You · Human review

    Draft v2 returns for fresh review

    Owner ↔ Agent

    Draft v2Awaiting review

    Resubmitted for fresh review

    6 / 10

  7. You · Human review

    You approve the exact v2 draft

    Host-owned local delivery

    Action approvalApproved v2

    Exact draft v2 + selected destination

    Only this version and destination are approved.

    7 / 10

  8. Host

    The Host delivers the approved local Markdown

    Host-owned local delivery

    Delivery

    Approved Markdown written locally

    Written locally; read-back verification is next.

    8 / 10

  9. Host

    Read-back confirms the delivered content

    Host-owned local delivery

    Verification

    Read-back matches the approved content.

    History

    Draft, feedback, decision and delivery stay inspectable.

    Local delivery verified · example

    9 / 10

  10. Host

    The Host waits for the next scheduled occurrence

    Host schedule & history

    Between occurrences

    The Host keeps time. The model is idle.

    Next occurrence

    A new draft gets its own review; earlier approval is not reused.

    Waiting for the next occurrence

    10 / 10
Illustrative drafts, decisions and receipt labels. Local Markdown review/revision/delivery has implementation evidence; this is not an external email, ERP, CMS or purchasing action.

Illustrative configuration and work records

Start the occurrence

Schedule → Agent

Responsibility
Weekly supplier note
Trigger
Friday · configured workspace timezone
Preparation
Read sources, write and check the draft.

Review & revise

Owner ↔ Agent

Draft v1
Prepared for owner review
Your feedback
“Include the source date for each delivery change.”
Revision
The agent adds the requested references.
Draft v2
Resubmitted for fresh review

Deliver what was approved

Host-owned local delivery

Action approval
Exact draft v2 + selected destination
Delivery
Approved Markdown written locally
Verification
Read-back matches the approved content.

Local delivery verified · example

Keep the responsibility

Host schedule & history

History
Draft, feedback, decision and delivery stay inspectable.
Between occurrences
The Host keeps time. The model is idle.
Next occurrence
A new draft gets its own review; earlier approval is not reused.

Waiting for the next occurrence

Illustrative drafts, decisions and receipt labels. Local Markdown review/revision/delivery has implementation evidence; this is not an external email, ERP, CMS or purchasing action.

Keep context through a decision

The pending item retains its content and feedback. Revision continues within the same allowance; approval does not restart preparation.

Check the effect

Approval permits the specified action. A delivery receipt establishes what actually arrived at the destination.

Use attention when it matters

Routine authorized work proceeds. Retained decisions and unresolved exceptions reach you with a concrete next action.

Configuration enables the team. Your assignment gives it direction.

Choose the sources, rules, output and action boundaries for the work you delegate. Explore the capabilities available to your team.

Explore business scenariosReview current capabilities