DEV Community

massiron
massiron

Posted on • Originally published at massiron.com

Building Controllable AI Agents: Why I Stopped Using Black-Box Tool-Spammers

The Problem with Most AI Coding Agents

If you've tried AutoGPT, CrewAI, or similar agent frameworks, you've probably seen this: the agent starts spamming tools in random order, writes files without telling you, and when something breaks — it just retries silently. Debugging becomes impossible because there's no trace of what the agent was thinking.

I ran into this wall while automating PR reviews for an open-source project. The agent would attempt a git merge, fail, then try something else — and I'd only find out after a CI failure. I needed controllable, auditable execution, not a black box.

Enter Deepstrain

Deepstrain is a terminal-native AI execution substrate. It's model-agnostic (works with Ollama, Claude, GPT-4o, DeepSeek, any OpenAI-compatible backend), antifragile, and built around plan-first execution. Before touching any files, the agent writes a plan you can review and approve.

Here's a real example: I wanted to refactor a Python module — rename a function, update all call sites, and run tests. With Deepstrain, I ran:

deepstrain run "Rename `calculate_total` to `compute_sum` in src/ and update all usages. Run tests after."
Enter fullscreen mode Exit fullscreen mode

Deepstrain first printed a plan:

Plan:
1. Read src/calculator.py to find `calculate_total` definition
2. Read tests/test_calculator.py to find usages
3. Use `sed` to rename in both files
4. Run `pytest tests/` to verify
Enter fullscreen mode Exit fullscreen mode

I reviewed it, hit 'y', and watched each step execute with full logging. Every command, every file read/write, every error — logged with stack trace. When a test failed because I forgot a second import, the error was captured, the agent adjusted, and I could see exactly what changed.

Key Features That Matter

  • 52 built-in tools: file I/O, git, bash, network, database, MCP server — all sandboxed and logged
  • Deterministic code analysis via atlas integration: no hallucinations in code understanding, because it uses actual AST parsing
  • Inspectable cognition: every decision is logged with context. You can replay the entire session
  • Antifragile: rotating error logs, graceful degradation. If a tool fails, the agent doesn't crash — it reports and retries with a different approach
  • Model-agnostic: run with Ollama locally (free, no data leaves your machine) or bring your own API key (e.g., DeepSeek at ~$0.009/task)

Trade-offs (Being Honest)

  • Terminal-native: no GUI. If you prefer a visual interface, this isn't for you.
  • Learning curve: the plan-first workflow takes getting used to. You can't just fire-and-forget.
  • Pro license: $9/month for HMAC activation and priority support. The free mode gives read-only tools (file reading, git log, etc.) — useful for auditing but not for writing code.

Where It Shines

  • CI/CD pipelines: run automated refactoring with full audit trails
  • PR review automation: read diffs, suggest changes, run tests — all logged
  • Open-source maintenance: bulk rename, migrate imports, generate test stubs
  • Local-first development: pair with Ollama for a completely offline AI assistant

Getting Started

pip install deepstrain
Enter fullscreen mode Exit fullscreen mode

Then grab a trial key from the repo or run with a local model:

deepstrain --model ollama:codellama run "Explain the architecture of this project"
Enter fullscreen mode Exit fullscreen mode

No cloud dependency. No vendor lock-in. Just a terminal, a model, and a plan.


Deepstrain is open-source (MIT license) on GitHub. Pro features are $9/month. More details at massiron.com/deepstrain.


Install: pip install deepstrain
Repo: https://github.com/mete-dotcom/deepstrain
Site: https://massiron.com/deepstrain

Top comments (0)