Flowent

Just say what you need. Flowent gets it done.

Flowent takes your request, works through the context and constraints, and chooses a practical way forward. It can research the problem, write code, call tools, or build a workflow, then keep going until the task is complete or your input is needed.

Capabilities

Flowent turns a conversation into action. It decides what should happen next, uses the capabilities available to it, and follows the work through.

You might ask it to:

  • Investigate the available options and recommend one that fits your needs.
  • Find a problem in a project, fix it, and verify the result.
  • Automate a repetitive task and run it every day.
  • Diagnose a failed workflow, repair it, and continue the run.

Flowent combines research, code, files, commands, models, MCP servers, and skills around the same goal. Work that benefits from structure, repetition, or scheduling can become a workflow that Flowent creates and manages for you.

Workspace

The Workspace keeps every step of the task visible.

In the Workspace, you can follow the conversation, tool calls, command output, progress, and results as one continuous task.

If Flowent turns the task into a workflow, open Workflows to inspect the actual nodes, connections, inputs, and outputs. Ask Flowent to maintain it, or open the canvas and change the properties, connections, and inputs yourself.

Flowent handles the complex work, while you can inspect and edit the execution whenever you want.

Workflows

Flowent completes simple requests directly and turns structured, repeatable, or scheduled work into workflows. A workflow can accept input, run agents and Python code, call tools, produce output, and run on a timer.

When a workflow fails, Flowent receives the execution details. It can locate the failed step, decide what needs to change, repair the workflow, and verify it again.

The usual loop looks like this:

Tell Flowent what you want to accomplish
        ↓
Flowent considers the options and starts the work
        ↓
Finish directly or create a workflow
        ↓
Run, inspect, and maintain it
        ↓
If something fails, Flowent diagnoses, repairs, and continues

Security

Flowent combines capable local tools with clear security boundaries.

  • File tools work within the workspace and explicitly allowed paths.
  • Additional access goes through permission review.
  • Risk review can stop broad, destructive, or sensitive actions before execution.
  • Commands use Bubblewrap on Linux, Seatbelt on macOS, and native Windows protection, with write access limited to approved locations.
  • If command protection cannot start, the operation stops instead of running without protection.
  • On Windows, the first protected command, or a later protection setup refresh, asks for system approval to create or repair a dedicated local group, restricted local accounts, and a network rule. Flowent resumes the command after setup completes.

You can give Flowent useful tools while keeping their reach visible and controlled.

Providers

Choose the models and services that fit your work. Flowent supports:

  • OpenAI-compatible Chat Completions APIs.
  • OpenAI Responses APIs.
  • Anthropic-compatible APIs.
  • Gemini-compatible APIs.
  • Custom service addresses and model names.

Provider settings include the selected model, reasoning effort, and context window. Flowent tracks context usage and can compact a long conversation so Flowent can continue with the goal, constraints, and completed work intact.

MCP servers and skills extend Flowent with more tools while your way of working stays the same.

Channels

Channels bring Flowent to the places where work already happens.

The Web workspace provides the full conversation, tool, and workflow experience. Telegram is available for sending requests and receiving replies away from the browser, with an approval step for new chat sessions.

Flowent keeps the same identity and task runtime across Channels. Its channel architecture is ready for more integrations alongside Web and Telegram.

Quick start

The next npm and PyPI release will include the Flowent runtime, web app, file search, and the files needed for command protection. Packages cover GNU/Linux with glibc 2.17 or newer, macOS 11 or newer, and Windows on x64 and arm64. Linux packages include Bubblewrap, macOS uses the Seatbelt service provided by the operating system, and Windows packages include the native protection helper. npm and pip select the matching package, so uv, Bubblewrap, and ripgrep do not need to be installed separately.

The currently published 0.3.10 packages predate this bundled runtime. Use Docker Compose or source development until the next release is available.

After the next release, install Flowent with npm (Node.js 20.9 or later):

npm install -g flowent

Or, after the next release, install it with pip (Python 3.11 or later):

pip install flowent

Start Flowent:

flowent

Open the address shown in your terminal and tell Flowent what you want to do.

To check whether your system is ready:

flowent doctor

The check reports command protection, file search, and built-in runtime files. On Windows, it reports when setup is required; the approval prompt appears when Flowent runs the next protected command.

Docker Compose

You can also run Flowent with Docker Compose:

git clone https://github.com/ImFeH2/flowent.git
cd flowent
docker compose up

The image includes its runtime, file search, and command protection requirements. You don't need to install uv, Bubblewrap, or ripgrep on the host.

Development

Flowent is under active development.

Source development uses pnpm, uv, the Rust toolchain, and system ripgrep. Linux also needs Bubblewrap. On Debian or Ubuntu, install the system tools and start the development server with:

sudo apt-get install bubblewrap ripgrep
pnpm install
uv sync --project backend
pnpm dev

Or run the development container:

docker compose -f docker-compose.dev.yml up

License

Flowent is released under the Apache License 2.0.