daAgent harness01
Give an agent more than a chat loop.
Planning, files, context management and delegation in one extensible harness. A useful starting point when a task takes more than one tool call.
Try buildingA research assistant that gathers evidence and writes a report.
Know first Constrain tool permissions and require approval for consequential actions.
Choose this when… +
- Choose it
- You need planning, files and delegated steps in an agent, without assembling each piece yourself.
- Skip it
- A single prompt or deterministic script solves the job. A harness adds state and failure modes.
- Consider instead
- LangGraph for a custom execution graph ↗
- Skills & hardware
- Python or TypeScript; tool permissions and testing. API models need network access; local models need their own inference hardware.
- Setup
- 30–60 min for a small prototype (estimate). Not a measured installation time.
</>Coding agent02
Choose the coding agent. Keep your model choice.
An open-source coding agent for working in a real repository. Worth exploring if you want to choose your provider rather than commit to one model ecosystem.
Try buildingA small feature in an existing app, with tests and a reviewable diff.
Know first Review generated changes. Model usage and hosted services can still cost money.
Choose this when… +
- Choose it
- You want a coding agent in your repository with a choice of model providers.
- Skip it
- Your team needs a particular editor integration or enterprise control this project does not supply.
- Consider instead
- Aider for a different terminal-first workflow ↗
- Skills & hardware
- Git, code review and a project test command. Ordinary development machine for hosted models; local model requirements vary.
- Setup
- 15–30 min with a configured provider (estimate). Not a measured installation time.
AaDocument processing03
Your PDFs deserve better than copy and paste.
Convert documents into structured representations for search, retrieval and downstream AI. Start here before building another chatbot on messy source files.
Try buildingA searchable document library with structure and page references.
Know first Check extraction quality on your own layouts, tables and scans.
Choose this when… +
- Choose it
- Layout, tables and multiple document formats matter to your retrieval pipeline.
- Skip it
- You only need text from a simple text-based PDF. Start with a smaller parser before adding model assets.
- Consider instead
- pypdf for a text-PDF baseline ↗
- Skills & hardware
- Python; extraction-quality checks. Requirements depend on the pipeline and models. First run can download assets.
- Setup
- 20–45 min including initial downloads (estimate). Not a measured installation time.
↗Web data04
Turn a website into something AI can actually read.
A self-hostable crawler that turns web pages into Markdown and structured data. Useful when the hard part of your AI workflow is getting usable source material.
Try buildingA research pipeline that collects public pages with their source URLs.
Know first Respect site terms, robots policies and rate limits. Do not bypass access controls.
Choose this when… +
- Choose it
- You need repeatable web collection with browser-backed extraction and Markdown output.
- Skip it
- An official API or a direct download already gives you the data. Prefer that simpler, permitted path.
- Consider instead
- An official API, or Playwright for custom browser logic ↗
- Skills & hardware
- Python; selectors, site policies and rate limits. A supported browser runtime; parallel crawling uses extra memory.
- Setup
- 20–45 min including browser setup (estimate). Not a measured installation time.
uLocal AI & training05
Make open models your own.
Run and fine-tune supported models with a local interface and training tools. A practical route from using a model to adapting one to a specific task.
Try buildingA fine-tuning experiment with a small, carefully checked training set.
Know first This release is a beta. Check GPU memory, model licences and training data rights.
Choose this when… +
- Choose it
- You have a measurable task, rights-cleared training data and a supported model to adapt.
- Skip it
- You have not tried retrieval, better prompts or evaluation first. Fine-tuning is not a way to invent missing facts.
- Consider instead
- Ollama when you only need to run a supported model ↗
- Skills & hardware
- Dataset preparation, evaluation and Python or the project UI. Model, quantisation and training method determine GPU and memory needs.
- Setup
- 45–90 min for environment and a small experiment (estimate). Not a measured installation time.
v_Model serving06
Go from a model on disk to a model people can use.
Serve supported open models through an API, with batching and memory-conscious inference. Explore it when your project needs a shared model endpoint.
Try buildingAn internal model API, benchmarked against your actual workload.
Know first You own hardware, authentication, monitoring and capacity planning.
Choose this when… +
- Choose it
- Several users or services need an inference endpoint, and you can operate the infrastructure.
- Skip it
- You need a first local experiment or do not want to own capacity, access controls and monitoring.
- Consider instead
- Ollama for a simpler local starting point ↗
- Skills & hardware
- Model serving, deployment, authentication and load testing. Supported accelerator and enough memory for the chosen model and workload.
- Setup
- 45–90 min with provisioned hardware (estimate). Not a measured installation time.