How Elyntic works

A message comes in. Work comes back for review.

Elyntic understands the request, prepares the work, and returns the result for your decision.

One requestEmail becomes visible work

Elyntic worksYou decide

DepartmentClient strategy

ProjectQ2 review

Request arrives

SourceMaya Chen / Northstar Studio

GoalPrepare Friday's strategy review

Project Kanban

Q2 strategy review

ViewKanban

Ready0
Assigned work
Agent work0
Plan and tools
Human review0
Decision point
Email / InboxEmail

Build the Q2 strategy review deck

Use the Q2 results and research for Friday's review.
Due FridayElyntic planning

The simple path

The message, work, and decision stay together.

One request keeps its context from the inbox to the final review.

Early-access limit: Gmail is the first complete communication path. Not every message or channel receives a fully automatic specialist and finished result yet.

1 / Understand

Find the history behind the request.

The earlier promise changes what the new message means.

  1. 1

    Read the selected history

    Gmail backfill can include sent and received full-body messages with resumable checkpoints.

  2. 2

    Find the people and promises

    Elyntic organizes identities, topics, questions, commitments, and signs of urgency.

  3. 3

    Decide what becomes work

    Important Gmail items can create a task; lower-priority messages can remain history.

Why this message matters
“Can we review the plan next week?”
Relationship
A client you have worked with for two years.
Earlier promise
A quarterly review before the next budget decision.
Decision
Which times, agenda, and note get sent.

2 / Work

Use the capabilities that move the job forward.

The value is what the extensions let the agent do, not how many extensions exist.

Plan and executeWorking

Start from a project, inspect the plan, and follow tool activity.

Create documents and codeImplemented

Read and edit files, compare changes, and reverse them.

Work from GmailWorking

Use email context, draft replies, and schedule or send through the configured path.

Manage tasksPartial

Create and move work on boards. Natural-language board control is still being connected.

Use browser and research toolsPreview

Local previews work; broader browser and research paths depend on runtime setup.

Delegate to more agentsPreview

The interface exists, but the default path is not yet dependable for every job.

3 / Review

The AI prepares. You decide what happens.

Routine work can move while sends, spending, and exceptions stay visible.

  1. 1

    Agents can

    Plan, research, create tasks, edit files, and prepare replies inside the limits you set.

  2. 2

    People decide

    Choose goals, handle exceptions, and approve consequential sends or spending.

  3. 3

    Elyntic records

    Keep the source, work, evidence, approval state, and result together.

Current limit: approval checks do not yet cover every tool path. The site does not claim universal pre-action approval.

Connections

Each connection gives Elyntic a different kind of context or action.

Gmail is the first full path. The others add useful context without pretending they all work alike.

Gmail
Reads history and starts workElyntic can read selected sent and received history, triage new messages, create eligible tasks, and draft or send through the configured account.
iMessage
Adds personal conversation contextOn a configured Mac, Elyntic can read permitted history and triage messages. It is not yet the same automatic task path as Gmail.
Slack
Adds team contextChosen messages, mentions, and threads can inform the work or be triaged when asked. Continuous Slack-to-task routing is not yet claimed.
SMS
Adds text-message contextConnected provider messages can enter triage. Availability and actions depend on the provider you set up.
Outlook / IMAP
Reads and sends emailBasic retrieval and sending work without Gmail-level history processing or task automation.

Why this is more than chat

The work has an owner, a goal, and a record.

Elyntic is being built to remember the operating model behind the task, not only the conversation that started it.

Agent workspace
Plans the job, uses permitted tools, and prepares the result.
Company system
Connects the main goal to departments, projects, tasks, budgets, approvals, and outcomes.
Background service
Checks for ready work, dispatches within limits, and records completion.
Technical names and current limits

Helios Agent is the execution layer. HBO is the company and work graph. The daemon is the recurring service. Harada-inspired goal cascades and department intelligence remain in development and are not a closed autonomous loop today.

Start with one real request

Show us the message and the work you need back.

Request early access