weftcloud
Request early access

HOW WEFT CLOUD WORKS

Pass the work.
Keep the understanding.

You talk to your coding agent. It manages the workers. Cloud keeps the team’s tasks, decisions and progress together across machines.

01 / A SHARED HANDOFF

The next person can start where you left off.

Your agent records a task, its acceptance criteria and the decisions behind it. A teammate’s agent retrieves those records from the hosted project.

You keep one conversation with your agent. It launches and manages workers, follows their progress, and brings you results and questions.

TWO PEOPLE / ONE PROJECT RECORD
YOUR MACHINEYour agent records the task.Add a CSV export · preserve original dates
WEFT CLOUD / SHARED PROJECTThe task. The decision. The reason.Keep original dates to preserve the source history.
YOUR TEAMMATE’S MACHINETheir agent picks up the work.Retrieves the same task and decision.
A teammate’s agent retrieves them on another machine.

Illustrative example · plays through and repeats.

See the agent conversation
AGENT / WORK RECORDCloud · one hosted project across people and machines
  1. Your agent · your machine
    Record the task, acceptance criteria and the decision to preserve original dates.
  2. Weft Cloud
    Task and decision saved in the hosted project.
  3. Teammate's agent · another machine
    Retrieve that same task and its decision. Continue the importer.
  4. Teammate's agent → Weft Cloud
    Record progress and the checks performed.
  5. Your agent
    Read the updated work record. Inspect the evidence before the next step.
Illustrative team workflow. Playback changes this example only.
Source and scope

Cloud hosts shared project state. OSS retains its complete local process and local SQLite records; it does not provide this hosted cross-machine workspace. Keeping state in Cloud does not itself run a test or prove a change correct.

02 / REMEMBER THE REASON

Your answer belongs to the project.

Ask your agent to check prior decisions before changing something significant. If there is no answer, it brings the choice to you and records your reply and its reason.

The next person’s agent can consult the same knowledge base. Changing sessions or machines needn’t mean explaining the decision again.

A QUESTION ONCE / AN ANSWER TO BUILD ON
  1. 01
    AGENT SEARCHES PROJECT MEMORYNo prior answer about export dates.
  2. 02
    AGENT → YOU“Keep the original dates?”Example reply: “Yes. The history matters.”
  3. 03
    AGENT RECORDS YOUR ANSWERKeep original timestamps.Reason: preserve the source history.
  4. 04
    NEXT PERSON’S AGENT“Found the decision and its reason.”
Another person’s agent can consult the shared record.

Illustrative example · plays through and repeats.

Follow the question, reply and later retrieval
AGENT / WORK RECORDCloud · hosted decisions shared across machines
  1. Your agent
    The importer could change existing dates. That changes the meaning of the records.
  2. Your agent → Weft Cloud
    Search the project's prior decisions about import timestamps.
  3. Shared project records
    No matching answer found.
  4. Your agent → you
    Keep the original dates, use the import date, or ask before changing them?
  5. You
    Keep the original timestamps.
  6. Your agent → Weft Cloud
    Record the decision and its reason in the shared project. Keep the original timestamps.Reason: People use dates to understand the order of their records.
  7. Your teammate's agent · another machine
    Retrieve the same project decision before continuing the importer. Keep the original timestamps.
Illustrative replay, based on recorded agent workflows. Playback changes this example only.
Source and scope

Your agent checks prior guidance and asks when a significant choice remains unresolved. Cloud keeps the resulting project record available across people and machines. Local OSS also supports the ask-and-remember loop; Cloud adds hosted shared state. This is an illustrative team handoff, not a claim that the historical study measured this particular two-person exchange.

03 / A PLACE TO RUN THE WORK

Keep the tools.
Choose where the task runs.

Use your own workers when the work belongs near your tools. For a separate environment, a cloud worker runs an uploaded workspace through the workflow and returns a patch.

Choose an available engine and model for the task. Follow activity and worker status in the dashboard, then inspect and integrate the result.

Put review before acceptance →
CHOOSE WHERE THE TASK RUNS
YOUR AGENTDispatch a well-defined task.Choose the worker, engine and available model.
YOUR MACHINEYour tools nearby
CLOUD WORKERSeparate environmentUploaded workspace → patch
RESULT + RECORDED PROGRESSInspect and integrate the work.
Follow the result, then inspect and integrate the change.

Illustrative example · plays through and repeats.

ALREADY HAVE A SOFTWARE FACTORY?

Keep your process.
Skip building the shared services.

Weft’s included software workflow gives you a starting point. Ask your coding agent to adapt the YAML to your stages and checks. You can write your own plugin when a process needs new tools.

Workflows, workers and local project memory are included in OSS. Cloud adds hosted shared records and AI review; your existing agents and CI still have a job.

YOUR AGENTS + YOUR CI
  1. Plan
  2. Implement
  3. Your checks
  4. Accept
Shared project recordsTasks · decisions · progress

Reuse the process. Inspect the outcomes. Adjust the next run.

BRING THE AGENT YOU USE

Give it a shared place to work.

Connect a compatible coding agent through the Weft CLI or MCP. Keep each person’s configured model access.

Using Dots or another everyday assistant?

Connect Weft to the coding agent your assistant delegates to. That agent needs Weft CLI or MCP access in its environment. A direct Dots integration has not been tested.

START SMALL

One useful task first.

Request access, connect your agent and record a task with a checkable result. Try a shared handoff before bringing in more work.

Choose local or shared records →
YOUR NEXT PROJECT

What would you put in motion?

Request early access to Weft Cloud. Start with your own coding agent, or bring your team and the agents they already use.

Request early access ↗