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 run inside a Bubblewrap sandbox with controlled filesystem access.
- Sandbox failures return to review before any broader retry is considered.
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
Flowent requires Bubblewrap for tool isolation and ripgrep for file search.
Install the system requirements:
sudo apt-get install bubblewrap ripgrep
Install Flowent with npm:
npm install -g flowent
Or install it with pip:
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
Docker Compose
You can also run Flowent with Docker Compose:
docker compose up
Development
Flowent is under active development.
Install the repository dependencies and start the development server:
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.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file flowent-0.3.10.tar.gz.
File metadata
- Download URL: flowent-0.3.10.tar.gz
- Upload date:
- Size: 1.3 MB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/6.1.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
e1519286fd7498a365a0eafbe620c32f47c0917f205b897d7f940dd9b755262a
|
|
| MD5 |
bc3bb937117b52b3225b1a29d4f7a18d
|
|
| BLAKE2b-256 |
1cc85ad2cd5b5f2172c16a5c62e7b96768ff1f59a4c8dc0282b434655d85a99c
|
Provenance
The following attestation bundles were made for flowent-0.3.10.tar.gz:
Publisher:
pypi-publish.yml on ImFeH2/flowent
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
flowent-0.3.10.tar.gz -
Subject digest:
e1519286fd7498a365a0eafbe620c32f47c0917f205b897d7f940dd9b755262a - Sigstore transparency entry: 2212544465
- Sigstore integration time:
-
Permalink:
ImFeH2/flowent@d45cc057ff1f787183118f2e0b4482ea8d29734a -
Branch / Tag:
refs/tags/v0.3.10 - Owner: https://github.com/ImFeH2
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
pypi-publish.yml@d45cc057ff1f787183118f2e0b4482ea8d29734a -
Trigger Event:
push
-
Statement type:
File details
Details for the file flowent-0.3.10-py3-none-any.whl.
File metadata
- Download URL: flowent-0.3.10-py3-none-any.whl
- Upload date:
- Size: 1.3 MB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/6.1.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
d7fb6406167058967a55ffc5cea5cccdae5959264431f9553e45a195d8aa7c9b
|
|
| MD5 |
0e3423fa051487ae06ece8fbf93a5db0
|
|
| BLAKE2b-256 |
e1dad57efab0542e4249509c1dd8e032a766d4a0a6ae8209d2fd6d098b893cc7
|
Provenance
The following attestation bundles were made for flowent-0.3.10-py3-none-any.whl:
Publisher:
pypi-publish.yml on ImFeH2/flowent
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
flowent-0.3.10-py3-none-any.whl -
Subject digest:
d7fb6406167058967a55ffc5cea5cccdae5959264431f9553e45a195d8aa7c9b - Sigstore transparency entry: 2212544490
- Sigstore integration time:
-
Permalink:
ImFeH2/flowent@d45cc057ff1f787183118f2e0b4482ea8d29734a -
Branch / Tag:
refs/tags/v0.3.10 - Owner: https://github.com/ImFeH2
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
pypi-publish.yml@d45cc057ff1f787183118f2e0b4482ea8d29734a -
Trigger Event:
push
-
Statement type: