INSIDE THE LOOP — THE HARNESS IN DEPTH

Give agents real work. Keep control of every step.

My Loop turns a request into a governed delivery run. It assembles context, isolates the code, executes your pipeline, validates every artifact and stops at the human gates you define.

  • 1:1 · One task, one isolated worktree
  • ∞ · Custom pipelines and stages
  • 24/7 · Schedules, webhooks and Bot
A task starts with a project, pipeline, agent and explicit context. My Loop creates the isolated workspace and carries the run from intake to pull request.

THE PARTS THAT MAKE THE LOOP RELIABLE

Built for long-running work, not one-shot prompts.

My Loop keeps the operational details that agent demos skip: memory, ownership, resumability, audit trails and explicit control over external actions.

MEMORY

Brain — memory that compounds

A local-first wiki memory. Agents recall past decisions before every stage and record what they learned after. Your loop gets smarter every run.

CONTEXT

Your codebase, indexed

An incremental context index feeds the right files and snippets into every prompt. Agents work like they've read the repo — because they have.

ARTIFACTS

Deliverables, not chat logs

Stages emit structured artifacts — Context Briefs, RFCs, ADRs, PRDs, review verdicts — validated and persisted, on the board or in the repo.

CONNECTORS

Work arrives on its own

Connectors for GitHub, Linear, Slack, Telegram, Sentry, Stripe and Postgres. A Slack thread or Telegram message becomes a task; approve and follow progress from your phone.

WORKTREES

Isolated by design

Every task runs in its own git worktree and branch — agents never touch your working tree. Turn on Squad mode and a manager splits a stage across parallel sub-agents.

BOT

Runs when you choose

Bot triggers pipelines on a schedule or webhook. Sprints track progress. Step away and return to reviewable work, not an opaque chat log.

A HARNESS, NOT ANOTHER CHAT WINDOW

Every run has structure before an agent writes a line.

The board is only the control surface. Underneath it, My Loop builds a repeatable execution envelope around every agent so the output can be inspected, resumed and trusted.

My Loop — a real My Loop Task Mission Control with a signal grid for task, run, changes, tests, runtime, deliverables, dependencies and activity

A task starts with a project, pipeline, agent and explicit context. My Loop creates the isolated workspace and carries the run from intake to pull request.

The My Loop board with demo tasks moving through the Context, Build, Review and Loop pipeline stages

Every column is a stage, every stage runs an agent — and human gates wait for you. The board morphs to whatever pipeline you pick.

  1. 01 / INTAKE

    Normalize the request

    Create work manually or receive it from GitHub, Linear, Slack, Telegram, Sentry, Stripe and Postgres.

  2. 02 / CONTEXT

    Assemble what the agent needs

    Repository indexing, project instructions, issue history and Brain memory become a focused context brief.

  3. 03 / EXECUTE

    Run in isolation

    A dedicated branch and git worktree keep the task away from your working tree. Squad mode can split a stage across parallel sub-agents.

  4. 04 / VERIFY

    Validate real deliverables

    Stages emit typed artifacts, tests, reviews, RFCs and ADRs. Guards can reject incomplete or malformed work before it advances.

  5. 05 / SHIP

    Stop, approve or continue

    Human gates hold external actions and merges. Approved work proceeds to a pull request with its full history intact.

DELIVERY EVIDENCE

From the request to a map of what changed.

A finished Build leaves more than agent prose. Diff, deliverables, evidence, Change Map and Mermaid stay attached to the task so Review can verify the work that actually landed.

01

Build leaves an artifact

The successful worktree state becomes a persisted Change Map instead of a temporary preview that disappears between stages.

02

Review has to show its work

Approval requires concrete evidence: a file and line, a test, or a command and its outcome.

03

You review one delivery record

Git Changes shows the raw diff while Change Map and Mermaid explain the same persisted result before you open the pull request.

UNDER THE HOOD

Watch My Loop turn intent into governed work.

Six short scenes reveal the machinery behind every task — from understanding a repository to producing evidence a human can trust.

01

01 / INTAKE

A request becomes governed work.

My Loop turns an informal ask into a task with a project, priority, pipeline and the policies that will govern the run.

The agent starts with a contract, not a blank prompt.
02

02 / CODEBASE

The repository becomes a live context index.

Files are mapped once, then only changed code is read again. Lexical, semantic and structural signals stay ready without repeatedly scanning the whole repository.

Large codebases stay fast, current and economical.
03

03 / RECALL

A question finds the right context — not the most text.

My Loop blends exact matches, meaning, code relationships, project memory and decisions, then ranks a bounded set of context for the agent.

Less noise goes in. More relevant work comes out.
04

04 / ISOLATION

Every task gets room to work safely.

A dedicated worktree — or a cloud sandbox when needed — keeps agent changes away from your active checkout while preserving the real project environment.

Your working tree stays yours until review.
05

05 / EXECUTION

One objective becomes coordinated execution.

Pipelines choose the stages. Subtasks expose progress. When work can run in parallel, a manager coordinates specialized agents and reconciles one deliverable.

Parallel work stays visible instead of becoming parallel chaos.
06

06 / REVIEW

A diff arrives with evidence, cost and a decision point.

Verification, screenshots or video, Mermaid diagrams, activity and usage travel with the change. A human gate decides what happens next.

You review the result and the proof — not an agent's confidence.

TECHNOLOGY ATLAS

Open the system, one capability at a time.

A practical tour of the infrastructure that makes My Loop reliable. Technical enough to be credible, clear enough to understand without becoming an indexing expert.

Understand

How My Loop turns a living codebase into useful context.

Execute

How plans become safe, coordinated changes.

Govern

How authority, dependencies and review stay explicit.

Operate

How automation keeps running and remains observable.

CONTROL IS THE COMMAND CENTER

Define the rules once. Every task inherits them.

Agent choice, concurrency, isolation, memory, review policy and Bot live in TDE Control. The harness is visible and configurable instead of being buried in prompts.

Control — the real TDE Control window: personal, hardware, system and AI & automation sections

A polished reconstruction of the real TDE Control surface. Content is anonymized; layout, right-side window actions and the Tonal Slate visual language follow the product.

PIPELINES THAT SHIP WITH TDE

Start opinionated. Change everything.

Start from the default, pick a template, or design your own pipeline — stage by stage.

Bring your own agent — Claude Code, Codex, Cursor, OpenCode — or run everything on TDE Pass models.

TEMPLATE / 01

GStack · Product Plan

From raw idea to shipped feature: Office Hours ideation → Research → Prototype → PRD → Issue Breakdown → Build → QA Gate. Product discipline, automated.

TEMPLATE / 02

Governed Delivery

For work that needs a paper trail: RFC → ADR → Work Item → Implement → Verify Guards → Human Approve. Every decision recorded, every merge gated.

MY LOOP

Start your loop.

My Loop ships with the free local TDE desktop. Add TDE Pass for selected open models at a flat price, or use local Ollama models offline.