intentic
Create your workspace
Create your workspace

Welcome to intentic

You delegate. Agents work. You approve.

A workspace for coding agents.

Create your workspaceDownload the app
The intentic fleet board: an Attention lane holding a Front Desk question and an agent asking one of its own, an Active lane with an agent working on a Stripe checkout, and a Finished lane where a completed change offers Land now. Each card carries a plain-English title, the model behind it, and what it has cost.The intentic fleet board: an Attention lane holding a Front Desk question and an agent asking one of its own, an Active lane with an agent working on a Stripe checkout, and a Finished lane where a completed change offers Land now. Each card carries a plain-English title, the model behind it, and what it has cost.
Open the live workspace
How it works

You bring the stone. The agents build.

Nothing is set in place without your word.

What you do

Agent Workspace

One board shows every agent you have running, and puts the one that needs you first.

See it →
acme-shop · /agents
The intentic workspace on the fleet board: an Attention lane holding a Front Desk question and an agent asking one of its own, an Active lane where a Stripe checkout agent is running two subagents, and a Finished lane where a completed change offers Land now. Every card carries its model, its branch, what it has cost and its diff stats. The chat docked beside the board holds the plan that agent wrote, with Approve under it.The intentic workspace on the fleet board: an Attention lane holding a Front Desk question and an agent asking one of its own, an Active lane where a Stripe checkout agent is running two subagents, and a Finished lane where a completed change offers Land now. Every card carries its model, its branch, what it has cost and its diff stats. The chat docked beside the board holds the plan that agent wrote, with Approve under it.

Integrations

Connect an agent to GitHub, Postgres, Stripe, Discord or any MCP server. Your keys stay on your machine.

See it →
acme-shop · /capabilities
The capability catalogue, twenty of them grouped by Platform, Code & issues, Observability, Data, Communication, Business & docs, Servers and Extend: GitHub, Sentry, PostgreSQL, Discord, Docker, Stripe, Obsidian, Outline, SSH and a VPN among them, seven marked as connected, and a row at the foot for any MCP server of your own.The capability catalogue, twenty of them grouped by Platform, Code & issues, Observability, Data, Communication, Business & docs, Servers and Extend: GitHub, Sentry, PostgreSQL, Discord, Docker, Stripe, Obsidian, Outline, SSH and a VPN among them, seven marked as connected, and a row at the foot for any MCP server of your own.

Automations

Start an agent on a failing pipeline, a new issue or a schedule. Every run opens on your board.

See it →

Approvals

The agent writes a plan and waits for your yes. Finished work sits on its branch until you read the diff.

See it →
acme-shop · /workspace
The workspace Changes tab: five uncommitted files grouped by repo with their line counts, and CheckoutPanel.tsx open beside them as a side-by-side diff: the removed lines in red on the left, the added ones in green on the right. The chat alongside holds the plan the change came from.The workspace Changes tab: five uncommitted files grouped by repo with their line counts, and CheckoutPanel.tsx open beside them as a side-by-side diff: the removed lines in red on the left, the added ones in green on the right. The chat alongside holds the plan the change came from.

Self-hosting

Move the workspace to a server so it runs without your laptop, and invite your team into the same one.

See it →
acme-shop · /sandbox/access
The acme-shop sandbox's Access page: the owner, a field to invite a teammate by email with their role beside it, the browsers currently signed in and a control that signs every one of them out, and under Here now a collaborator, Grace Hopper, looking at the agents board. The list on the left is everything else the box holds: environment, secrets, agent account, extensions, personas and devices.The acme-shop sandbox's Access page: the owner, a field to invite a teammate by email with their role beside it, the browsers currently signed in and a control that signs every one of them out, and under Here now a collaborator, Grace Hopper, looking at the agents board. The list on the left is everything else the box holds: environment, secrets, agent account, extensions, personas and devices.
Every feature, in detail →
Why a workspace

You cannot approve what you cannot read.

Agents write a lot of code, quickly. Checking it is the real work, so the tools for checking it are the product.

Here

What you get to look at.
  • The diff of every file, before any of it lands
  • The editor and the file tree, to look anywhere yourself
  • The same terminal the agent is typing into
  • The run as it happens, stoppable mid-thought
  • What every run cost, agent by agent

In a chat box

What you get instead.
  • A wall of text
  • An assurance that it worked

Nothing to open, and nothing to check.

Every agent works on its own branch, so nothing it writes touches the files you have open.

How reviewing agent work works →
What it costs

intentic is free. Agents use AI plans you already pay for.

You bring the AI plans, your machine does the work, and there is nothing to pay us.

Your agent accounts
Flat, not metered
  • We never meter your tokens or add a markup.
  • No cloud compute to rent. Agents run on the machine you start them on.
  • Everything is included. No tiers, no limits, no card.
About the creator

Artur Kurowski

Full-stack engineer, DevOps, and 15+ years of shipping production systems.

Developer's job has changed. We're now AI operators. It requires different toolset.

More about who builds this →

Why trust intentic?

Self-hosted. The platform holds only your identity and sandbox URL, never your code or keys.

What the platform actually holds →

Open source first

All of intentic is MIT on GitHub. No hidden binaries, no telemetry, nothing to trust blind.

Read the source →

It builds itself

Agents wrote most of intentic in public, and every commit they made sits in the log.

Read the commit log →

It is new

There are no customer counts, testimonials or maturity claims yet.

Getting started

Three steps to your first agent.

Sign in, paste one command, and your workspace opens.

in your browser

Sign in with Google

No forms and no card. We keep your email address and your workspace's address, and nothing else.

Your sandbox is waiting

Your sandbox is the private room your agents live and work in. We spin one up and give it its own web address, no Cloudflare account needed.

on your machine

Paste one command

One line starts it on your own machine. If Docker is missing, it offers to install that first.

your terminal
$ curl -fsSL https://intentic.dev/connect | sh

It sets up your workspace on your own computer. Nothing is deployed anywhere and no ports are opened.

This is one of two machines it can run on. Compare them

Rather not touch a terminal?

It runs the same command for you: Docker if the machine needs it, then the sandbox, then your workspace.

Get the app for Windows or Linux
FAQ

Before you install it.

What it costs, where your code sits, and what is not built yet.

What it is

The product, how it differs, and what it runs alongside.

What happens when I close the browser?

Nothing. The agents live on your machine, not in the tab, so terminals stay open and turns finish without you. Reopen from any device and the same fleet is there, sorted by who needs you.

What keeps an agent running when a machine sleeps →
How is this different from a custom GPT or a .md instructions file?

A custom GPT or instructions file changes what an assistant is told. It does not install tools or connect to your code. In intentic, an agent works inside a container with the tools, repository access and instructions it needs for the job.

How does this compare to Conductor, Cursor, OpenCode or Nimbalyst?

Claude Code, Codex and OpenCode can run inside intentic. Cursor can work beside it. Local orchestrators such as Conductor and Nimbalyst are the closest comparisons because they also manage several agents. Cloud platforms differ most in where your source code runs.

Every comparison, with the case for the other product →
Can I run a separate agent for each job?

Yes, that's the intended shape: a migrations agent, a storefront maintainer, a support agent, each with the access its job needs. Automations wake them on a schedule or an event.

Specialize a sandbox until it does a job alone →
Should I start a new sandbox or add a new persona?

Create a sandbox when a job needs different code, tools, connected systems or its own budget. Add a persona when the job stays the same but the agent needs to speak as a different public identity, such as a brand account instead of your personal account.

Specialize a sandbox, then grow a team →
Which AI models does it use?

Claude Code (Opus, Sonnet, Haiku), Codex, Grok, Kimi Code or Google, picked per conversation. Your provider, your account, your usage.

Getting started

What you need, what it costs, what it can touch.

What do I need to run a sandbox?

A computer with Docker and a Google account. You do not need a public IP address or any open inbound ports. If Docker is missing, the installer offers to install it after you confirm.

Do I need a Cloudflare account?

No. intentic provides the private connection by default. You can use your own Cloudflare domain instead; the setup token is used once to find the domain and is not stored.

Is any of it paid?

No. Every sandbox, capability and shared workspace is free, with no tiers, limits or card. All of intentic is MIT on GitHub. You pay your own model provider, directly.

Can the agent break my stuff?

An agent can make mistakes, so it starts by proposing a plan for you to approve. You can review or discard every file change, and changes to installed software need separate approval. You can change the agent's permissions at any time.

How to review what an agent wrote before you accept it →
Is it production-ready?

It is a working product, but it is new. Start with low-risk work and review the results. Every agent proposes a plan first, and every file change is shown as a diff before you accept it.

Ownership & privacy

Where your code, secrets and data actually sit.

Where does my code live?

On your machine. The sandbox runs where you start it, and your browser connects over a private tunnel. The platform stores your identity and the sandbox's URL. It never receives your files.

Where your code goes with any coding agent →
Can intentic read my secrets?

No. Your credentials stay inside the sandbox and never reach the platform. The platform stores only encrypted tokens that connect your browser to the sandbox. Secret files such as .env are never sent through that connection.

Giving an agent credentials without leaking them →
Is it open source?

Yes, all of it. The sandbox, CLI, workspace and platform are MIT-licensed in one public GitHub repo, so you can read every line that touches your code before you run it.

Can I export or delete my data?

Settings → Export downloads everything the platform stores about you as JSON. Deleting your account also deletes its sandbox records, sessions and access permissions.

Open-source and free forever

Contribute to our code, extend workspace
or offer services for others.

Create your workspaceSee the source