tm8
Book a demo
INSIDE THE WORKSPACE

People, agents and tools.
Working with context.

Capture an idea, coordinate the sessions and keep the result connected to the original goal. Explore the sample workspace below, then see how TM8 fits your team.

Runs right here in your browser. No account needed.
Launch workspaceInteractive demo
Sample data
THE WHOLE TEAM, IN VIEW

128 agents. One shared direction.

ResearchBuildDesignReview
Your team keeps the final say.Try the tabs. This is a working demo.
TM8’S META-HARNESS · THE COORDINATION LAYER

Give every agent
the bigger picture.

An agent runtime gives a session its tools. TM8 connects the sessions, people and work around it. These shared building blocks—called primitives—make that coordination possible.

In TM8, those building blocks are stored as connected records, or entities. Here is what they help you do.

Explore the building blocks 1 / 6
  1. 01 / Tasks

    Turn the idea into owned work.

    Break an outcome into tasks and subtasks. Connect dependencies so each agent can see its part in the larger job.

    Example

    Improve onboarding → research → build → review

    A shared plan instead of scattered requests.

  2. 02 / Sessions

    Give each agent a focused job.

    A session is a workspace record you can act on. Create a session, send it instructions and steer it as the work develops. Agents can create and coordinate other sessions too.

    Example

    A coordinator brings in a research agent and a build agent.

    Parallel work you can follow and redirect.

  3. 03 / Messages

    Let teammates talk to each other.

    People and agents can exchange instructions, questions and progress across sessions. Keep the conversation attached to the work it concerns.

    Example

    Research sends findings to the builder; the reviewer asks for a check.

    Less manual copying between separate chats.

  4. 04 / Shared records

    Carry the context beyond one chat.

    Connect documents, decisions and results to tasks and sessions. Give the next agent a way to find what happened, what exists and why the work matters.

    Example

    The brief, research notes and review evidence stay linked to the task.

    A useful starting point for the next teammate.

  5. 05 / Teammates

    Make people and agents visible.

    Work on your own or with a team. Keep responsibilities and agent activity in a shared workspace, using supported providers and the permissions your setup allows.

    Example

    A person sets the direction. A coordinator delegates. A person reviews.

    Clearer ownership across people and agent sessions.

  6. 06 / Relationships & graphs

    Compose a bigger plan with Craft.

    Parent–child links and other relationships connect the records. Craft arranges them into a graph; a complex part can contain a nested plan of its own.

    Example

    Project graph → implementation plan → tasks, sessions and results

    The details stay connected to the bigger picture.

Tools connect. Work coordinates. MCPs give agents access to configured tools. The WhatsApp bridge brings requests into the workspace. Connected machines let sessions exchange messages across servers.

Shared structure helps agents coordinate; results still depend on the brief, model, permissions and review. It does not guarantee error-free or duplicate-free work.

FROM ONE PERSON TO A SHARED TEAM.

Built for the whole job.

Turn an idea into a plan.

Capture the outcome. Break it into tasks and subtasks, link dependencies and give agents focused work.

Work solo. Work together.

Bring people and agents into a shared workspace where the brief, responsibilities and progress stay visible.

Coordinate agent sessions.

Create sessions, exchange messages and steer the work. Agents can involve other agents instead of leaving you to relay every update.

Carry the context forward.

Connect tasks, documents, decisions, memories and skills so a session can understand the larger job it belongs to.

Make the plan visible.

Use Craft to arrange connected tasks, sessions and results into graphs, including nested plans for more complex work.

Connect work across machines.

Coordinate agent sessions across connected local machines and servers, with messages that travel between them.

THE TEAM, WITHOUT THE TANGLE

Different focus.
Shared direction.

A session connects a conversation to an agent process. Agents can create other sessions, send messages and steer work. Keep research, implementation and review focused while the shared task holds the job together.

Shared project context
RESEARCH

Find the useful patterns

Compare approaches. Bring back evidence.

BUILD

Turn the plan into a change

Implement the agreed scope. Keep a clear trail.

REVIEW

Give the result a second look

Check the behavior against the original intent.

MAKE THE CONTEXT YOURS

A good starting point
for every teammate.

Jev helps prepare the context and coordinate agent communication. Your team chooses the direction.

Project

Connect the repository and working folder.

Knowledge

Bring the relevant documents, memories and skills.

Permissions

Choose the access each session needs.

MCPs & CONNECTORS

Your tools.
Part of the work.

Give agents access to the tools and information your workflow needs. Use configured MCP connectors and authorized accounts alongside the context in TM8.

  • Choose the connectors relevant to the job.
  • Connect the account the work should use.
  • Keep tool activity tied to a coordinated task.
Discuss your tools and setup
Documents & knowledge
Development tools
Business systems
MCP connectionConfigured tools · authorized account
Your agent sessionA focused task in a shared workspace

Conceptual flow. Not a list of preconfigured integrations.

MCP connects tools and resources. TM8 coordinates the work around them. Available connectors depend on your deployment, provider setup and permissions; connecting context does not grant access to another person's accounts.

WhatsApp ASK WHERE YOU ALREADY TALK

WhatsApp is a way into
your TM8 workspace.

Check what is happening, ask about a task or get an agent involved. The bridge connects the conversation to work in TM8, so a request can move beyond a chat reply.

01

Send the request

Ask a question, describe a problem or follow up on work in a connected WhatsApp conversation.

02

Find the relevant context

TM8 can use the tasks, sessions and records available in the connected workspace to understand the request.

03

Bring in a teammate

An agent can create or steer a session, delegate an investigation and keep the conversation informed.

04

Review the next step

Receive an update or a clarification question. Changes that require approval still need that approval.

Answers depend on the connected workspace, accessible context and permissions. Acknowledgement is not proof that the requested change is complete.

See the real WhatsApp example
CRAFT · A PLAN YOU CAN FOLLOW

See how the pieces
fit together.

Craft gives connected work a visual structure. Arrange tasks, sessions, teammates and documents into a graph, with relationships and nested plans when a job needs more detail.

SHARED OUTCOMEImprove the customer welcome
Understand the problemResearch session + findings
Build the agreed changeImplementation task + context
Review the resultChecks + human decision

Illustrative plan. Connected records give the team a shared structure.

Keep the larger goal visible. A session can understand the task it owns and the wider plan it belongs to.

Go deeper where needed. Break a complex part into a nested plan while keeping it connected to the original outcome.

CONNECTED ACROSS MACHINES

Different machines.
A shared conversation.

Work can span connected local machines and servers. Agent sessions on those machines can exchange messages through TM8 and stay connected to the work they are part of.

Deployment, model access and concurrency depend on your infrastructure and provider limits. This is coordination across connected systems, not a promise of unlimited capacity.

Shared TM8 workspaceTasks · context · messages
Local machineAgent sessions
Connected serverAgent sessions
Another serverAgent sessions
SEE THE ACTUAL PRODUCT

Now watch it at work.

The interactive examples above make the workflow tangible. The product tour shows the recorded interface, with chapters for the parts you care about.

Watch the recorded tour
CLEAR EXPECTATIONS

Where TM8 fits.

Why use TM8 alongside an agent coding tool?

An agent runtime handles a session and its tools. TM8 provides a shared place to coordinate multiple sessions, people, tasks and context. You can follow the larger job instead of managing each conversation in isolation.

What do you mean by a meta-harness?

A coordination layer around agent runtimes: shared tasks, session messaging, connected context and visibility into the wider work. You can use TM8 without learning that term.

Can one agent coordinate other agents?

Yes. Sessions are part of the workspace: agents can create sessions, send messages and steer work using the available capabilities. The brief, permissions, model and human direction still shape the result.

Does this prevent every mistake or duplicate task?

No. Shared context and explicit responsibilities make coordination possible, but do not guarantee correctness or eliminate duplicated work. Set clear outcomes, review evidence and keep people involved in consequential decisions.

Can we bring our own models and tools?

TM8 works with supported providers and configured connectors. Model usage is billed separately by your providers. Ask about the specific runtimes, tools and deployment your team needs; custom model hosting is a setup discussion, not an included service.

Make it your own

Bring us your next project.

Bring a recurring request, the tools involved and the people who need the result. We will map a TM8 workflow around your team.

Book a walkthrough
Practical workflows

A clear way to put agents to work.

Start with a small outcome, the right context and a review you can trust.

Parallel development

Start with independent outcomes. Share the constraints. Review the combined change before it ships.

Read the workflow

Shared context

Curate a small, relevant starting point. Keep decisions connected. Update the context when the work changes.

Read the workflow

Human review

Define the checks before work starts. Inspect the result. Keep the release decision separate from the implementation report.

Read the workflow