Otto-m8

Latest version: v0.0.2

Safety actively analyzes 723217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

0.0.9

What's Changed
* Breaking Changes: Dynamic Rendering of Block Data by farhan0167 in https://github.com/farhan0167/otto-m8/pull/75

From this point onwards, the frontend will no longer keep the block initialization logic. The backend will solely be responsible for what gets rendered, including what gets rendered on the blocks and the sidebar, to deciding how the run_config dictionary should be built to create a backend template.

**Full Changelog**: https://github.com/farhan0167/otto-m8/compare/0.0.5...0.0.9

0.0.5

What's Changed
* Issue 65 lambdas fc cleanup by farhan0167 in https://github.com/farhan0167/otto-m8/pull/66
* add param type in function calling by farhan0167 in https://github.com/farhan0167/otto-m8/pull/67
* Fix/dependencies missing instructions by farhan0167 in https://github.com/farhan0167/otto-m8/pull/69
* Issue 64 Introduction of Custom Code by farhan0167 in https://github.com/farhan0167/otto-m8/pull/70

All in all this version will mark the start of allowing folks to write custom code, and also change implementations of existing blocks. How custom code are different than Lambdas? With Lambdas you were writing custom code that got deployed as its own API which meant that if you deployed your workflow template on the cloud, you need to make sure your lambdas are also deployed and configured seperately. With custom code blocks, any custom code you write is deployed in the same docker container as your workflow. Furthermore, you aren't limited by how I implemented the starter blocks. You can now alter them to your liking.

**Full Changelog**: https://github.com/farhan0167/otto-m8/compare/0.0.4...0.0.5

0.0.4

What's Changed
* Redeployment and Edits Addressing Issue 35 by farhan0167 in https://github.com/farhan0167/otto-m8/pull/59
* Expect to be greeted in a new Home page where you can launch pre-made templates, or create a new one from scratch. Furthermore, you can now edit already deployed workflows.
* Change to full open source under the Apache License, aka all restrictions are removed.


**Full Changelog**: https://github.com/farhan0167/otto-m8/compare/0.0.3...0.0.4

0.0.3

This release introduces some major changes, which includes renaming of the `src` module to `otto_backend`. This was done, so we could expose some packages in the src folder for the new toolkit module(which is essentially the sdk for otto-m8).

What's new?

Tracer v1
A Tracer is essentially a logging utility for the workflow. Everytime a workflow is run, users would expect to see workflow and block level logs, which consist of the input, process and output of each block. This becomes important when you have a bunch of models interconnected. Usually you'd only see your input, and the output of the last block. All the intermediate block outputs are lost. With Tracer, you can now inspect each block.

SDK
With this release, you can now officially download otto-m8 from PyPi. Simply do `pip installl otto-m8` and interact with your deployed workflows. Example code:

python

from otto_m8.run import OttoRun
import json

Assuming your workflow is running on port 8001
otto = OttoRun(workflow_url='http://localhost:8001/workflow_run')

payload = otto.create_empty_payload()
print(payload) Do this to ensure you know the names of your input blocks

payload['Input_Block'] = "<insert your text>"

response = otto.run(payload)
print(json.dumps(response, indent=4))


Material UI
I'm starting to move away from Bootstrap. Realistically, its not helping me make my project look decent even though it was initially a good thing to start with to ship fast. But starting from this release, I'll be moving most of the components to material UI for consistency.

**Full Changelog**: https://github.com/farhan0167/otto-m8/compare/0.0.2...0.0.3

What's Changed
- Issue 54 tracer implementation and SDK by farhan0167 in https://github.com/farhan0167/otto-m8/pull/55
- Move away from requirements.txt files onto poetry for dependency management
- Create a package of the src. directory such that i can do a pip install otto_backend_engine from PyPi for the otto_m8_sdk(which will exposed to the client).
- /src/ module named to otto_backend. Hence why there's 97 files changed.
- Dashboard: Move away from React Bootstrap for a start, and transition to Material UI. Most for a cleaner UI. Goal for the future should be fully move to Material UI.
- SDK introduced for interacting with workflows
- Tracer v1 implemented: Get logs for each run of your workflow, including block level logs.



**Full Changelog**: https://github.com/farhan0167/otto-m8/compare/0.0.2...0.0.3

0.0.2

What's Changed
* Major Code Refactor and Input Parsing by farhan0167 in https://github.com/farhan0167/otto-m8/pull/45
* Add Document Parser:Langchain Integration 34 by farhan0167 in https://github.com/farhan0167/otto-m8/pull/46
* Introduction of Image Inputs and Faster Builds by farhan0167 in https://github.com/farhan0167/otto-m8/pull/47
* Add Multimodality for HF by farhan0167 in https://github.com/farhan0167/otto-m8/pull/48
* Input string handling and coming back to the JSON template by farhan0167 in https://github.com/farhan0167/otto-m8/pull/49

Features
- Run multimodal(Image/Text) huggingface models
- Faster Workflow builds. Previously used to take over a minute
- Start of Langchain Integration

**Full Changelog**: https://github.com/farhan0167/otto-m8/commits/0.0.2

Links

Releases

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.