AutonomyEfficiencyEvolution

Repository-aware tools for autonomous software work.

Autonomous Coding Workflow Runtime

Autonomous Coding
Workflows

Describe your goal. minitok plans, executes, verifies, and iterates within configured limits??좏릱hen stops safely for review if your checks do not pass.

Choose a plan
npm install -g @flotic/minitok@1.4.0
Read the docs
Local-firstYour repository stays yours.
Bring your own LLMYour keys, your model.
Provider-agnosticSwitch providers freely.

Why minitok?

AI coding agents generate code. minitok manages the workflow around them -- planning, verifying, and iterating until the goal is met.

Without minitok

  • Prompt every change manually
  • Review and correct output repeatedly
  • No automated verification

With minitok

  • Describe your goal once; minitok orchestrates
  • Verify and iterate within configured limits
  • Keep repository context across cycles

minitok is not another AI model. It is a workflow runtime that structures the task, controls execution, verifies results, and handles retry and recovery within configured limits — around whatever model you choose.

How It Works

A closed loop for every repository change, with explicit verification and safe-stop boundaries.

1

Describe

Tell minitok what you want changed in plain language.

Goal
2

Execute

minitok directs your coding agent.

Agent
3

Verify

Your checks validate the result.

Checks
4

Adapt

Failures guide targeted retries.

Retry
5

Deliver

An approved, verified result is applied to your working directory.

Result
✓ Verified result

Failsafe: if checks fail or configured limits are reached, minitok stops without merging the change. The normal approval applies one complete change set; file-by-file cherry-picking is not currently supported. If the final patch cannot be applied cleanly, it is preserved at .minitok/last-run.patch for inspection.

Autonomous work in practice

From a plain-language goal to a verified change

One goal, coordinated execution, and a result your checks can verify.

Illustrative fixture??좏릨ot live production evidence. ??좏뤁erified??means the configured checks passed; it does not guarantee correctness or production readiness.
Measured product outcomes

Clearer workflows, measured locally

Context compaction and bounded run history, without unsupported performance promises.

Measured character compaction and bounded local outcome persistence.
Context efficiency

Keep what matters

Compacts over-budget context while reporting the before-and-after size.

100,000 → 4,000 characters Fixture result, not a provider-token benchmark.
Inspectable outcomes

Carry verified results forward

Stores bounded local outcome history for targeted retries.

2 outcomes · 2 checks passed Persistence shown; model learning not claimed.

Built for Developers Who Ship

Core tools for real developer workflows.

Provider Agnostic

Use supported providers and switch without changing workflow.

Repository Intelligence

Changes use context from your actual codebase.

Goal-Directed Execution

Iterates toward your goal with bounded execution.

Budget Control

Set token limits and control usage.

Adaptive Runtime

Uses execution history to target retries.

MCP Integration

Exposes tools for external coding agents.

From Install to Verified Result

Install, configure your provider, describe the change, then review the result.

bash
# Check environment and configure your LLM provider
$ minitok doctor
??/span> Node.js ??22.19.0
??/span> LLM provider configured
??/span> Repository detected
 
# 3. Initialize workspace
$ minitok migrate
 
# 4. Describe the change
$ minitok run "Add input validation to the signup form"

Requires Node.js ≥ 22.19.0 and git. Bring your own LLM provider keys.

What Would You Build?

Describe a task in plain language; minitok runs the workflow.

Fix a bug

"Prevent duplicate signup accounts and add a clear error."

Ship a feature

"Add signup validation and tests; verify before completion."

Maintain a dependency

"Upgrade auth and fix the tests that break."

Security by Design

Protect credentials and control where code runs.

Signed entitlements

Only authorized installations can access protected minitok capabilities.

Encrypted credentials

Activation keys are encrypted at rest so sensitive credentials stay protected.

Protected sessions

Session boundaries help keep authenticated workflow access isolated and controlled.

Abuse-resistant service

Rate limits help protect public endpoints and keep access reliable.

Simple Pricing

Choose the telemetry boundary for your workflow.

Open
US$3.99/ month

Local-first workflow runtime

  • Consent-required per-run telemetry
  • 30-day retention
  • Repository-aware planning
  • Verify, review, and repair loop
  • Bring your own LLM provider
Choose Open
Recommended Select
US$4.99/ month

Local-first workflow runtime

  • Consent-required aggregate-only telemetry
  • 14-day retention
  • Repository-aware planning
  • Verify, review, and repair loop
  • Bring your own LLM provider
Choose Select
Private
US$6.99/ month

Local-first workflow runtime

  • No telemetry upload or storage
  • Telemetry stays local
  • Repository-aware planning
  • Verify, review, and repair loop
  • Bring your own LLM provider
Choose Private

LLM provider usage is billed separately. Monthly subscriptions renew automatically until cancelled. Cancel anytime through the Dodo customer portal; access continues through the current paid billing period, and cancellation stops the next renewal. The current paid billing period is not automatically refunded. No free trial. See the Cancellation Policy.

Frequently Asked Questions

Is this just another AI coding agent?

No. minitok is a workflow runtime that orchestrates your chosen model through planning, execution, verification, and retries.

Do I have to pay for an LLM separately?

Yes. Bring supported provider credentials and pay that provider directly for model usage.

Does minitok run locally?

Yes. minitok edits your working directory locally; code-generation requests go to your configured provider.

What do the plans include?

Open includes consented per-run telemetry for 30 days; Select, consented aggregate-only telemetry for 14 days; Private stores no telemetry. Each includes one installation and no free trial. Cancel anytime through the Dodo customer portal; access continues through the current paid billing period and the next renewal is canceled. The current paid billing period is not automatically refunded. See the Cancellation Policy.

Ready to Automate Your Workflow?

Make your next change verifiable.

Choose a plan