Skip to main content
DOBE

Files & operations

Send a job. Get the work back.

Send a request. Get the result back. Continue the same job in its thread.

Verified owner pilot
A real request and follow-up reply completed in the same task.

See how it works
Conceptual illustration of a message request reaching a laptop and returning a completed file

Workflow illustration · AI Employee

The job

Same business.
A better way through it.

Before

A useful AI workstation should be able to receive an authorized job without the owner typing directly into its desktop chat.

What DOBE built

DOBE built a private Slack connection that accepts messages from the approved owner, starts local Codex work, and returns results in the matching thread.

Watch the work move

From input to outcome.

Play the four-step explanation, or choose a step. This illustrates the workflow; it is not a recording of a live run.

Conceptual illustration of a message request reaching a laptop and returning a completed file

Workflow illustration

Follow the job

Start with your work.

An authorized owner's message in one private Slack channel

See every step
  1. 01

    The approved owner sends a new request in the designated private channel.

  2. 02

    The connection checks the sender, channel, and whether the event was already handled.

  3. 03

    A local Codex task performs the requested work within its normal permissions.

  4. 04

    The answer returns to the original Slack thread.

  5. 05

    The owner replies in that thread to continue the same task with its prior context.

  6. 06

    The completed replies are read back in Slack and matched to the local task record.

The result

Finished work.
Something you can check.

2

messages, verified replies

One initial request and one follow-up completed during the September 15, 2026 owner pilot.

1

continuing task

The follow-up resumed the same local Codex session and retained its earlier context.

What came out

Two real owner messages produced two replies in one continuing Codex task. The initial answer matched the workspace fact, and the follow-up correctly recalled the earlier test context. Both replies were checked in Slack.

This proves the owner pilot's request, execution, return, and continuation path. It does not establish phone notification delivery, client rollout, or unrestricted remote control.

Why it matters

The conversation and the result stay together. The owner can request work through a familiar messaging tool and follow up without restating everything.

The evidence, scope, and details

What was verified

Verified owner pilot · A real request and follow-up reply completed in the same task.

  • Real Slack request reached the owner Mac
  • The Mac read a real workspace fact
  • Final answer read back in the original thread
  • A second reply resumed the same Codex task
  • Sender and channel limited to the owner pilot

Tools: Slack · Codex · MacBook · Local workspace

What the test actually did

The first request asked the Mac to read a harmless workspace identity fact. The second checked that a word from the earlier exchange was still available in the same task. Local execution records and Slack reply readback support both steps.

The illustration uses generic message cards. It is not a screenshot of private work or a claim that a more complex customer job was completed in this test.

When the Mac can receive work

The Mac must be awake, online, and logged in. A message sent while the listener is offline is not guaranteed to replay; the owner should see an acknowledgment before relying on it.

The pilot covers approved text messages and thread replies. Attachments, other users, cloud workers, and customer installations are separate work.

More work. Same idea.

All case studies
Workflow illustration of four accounting exports being checked and organized through one MacBookVerified client systemWorkflow illustration

Files & operations

Four files. One clean database.

A guarded intake workflow turns four recurring accounting exports into one checked working database.

$69M+

in historical invoices organized

See the work
Conceptual illustration of payment paperwork being organized into checked recordsWorking demoWorkflow illustration

Files & operations

Payment PDFs. Into a ledger.

A working demo turns sample ACH payment PDFs into structured spreadsheet output with a visible review trail.

Working sample-data demo, not a client deployment.

See the work
Conceptual illustration of spoken ideas and written drafts alongside a MacBookLive product; automations pausedWorkflow illustration

Files & operations

Say it. Start a post.

The TalkEO product and public blog are live; its background generation chain is intentionally paused.

Public product surfaces are live; automatic generation is not currently operating.

See the work

Your job could be next

Want to give your computer a job without sitting at it?

Pick one useful task and the message channel you already use. We can define who may request it, what it may do, and how the result comes back.