Search Results for "web-based"

...Overall, Claw Code serves as a research-driven platform for advancing agent-based software development systems.

The Griptape framework provides developers with the ability to create AI systems that operate across two dimensions: predictability and creativity. For predictability, Griptape enforces structures like sequential pipelines, DAG-based workflows, and long-term memory. To facilitate creativity, Griptape safely prompts LLMs with tools (keeping output data off prompt by using short-term memory), which connects them to external APIs and data stores. The framework allows developers to transition between those two dimensions effortlessly based on their use case. Griptape not only helps developers harness the potential of LLMs but also enforces trust boundaries, schema validation, and tool activity-level permissions. ...

...The idea is to let developers or users harness an AI agent that can simulate clicking, typing, reading UI elements, and interacting with apps in a human-like way via the GUI, which can enable tasks like automated testing, scriptable workflows, or even autonomous usage of GUI-based applications. Because GELab-Zero is fully open-source and doesn’t require external services, it offers privacy and control: everything runs locally under your control. The project provides a lightweight base model (4B parameters in its public release) that can run on modest hardware (depending on quantization), making it more accessible than many large-scale AI solutions.

Harness-1 is a 20B search agent trained with reinforcement learning inside a stateful retrieval harness. It is designed for long-horizon search tasks where the model must search, inspect documents, curate evidence, verify claims, and decide when enough evidence has been gathered. The harness externalizes search state, including candidate documents, evidence links, verification records, and budget-aware context. This lets the policy focus on higher-level decisions instead of trying to keep...

Browser Harness is a self-healing browser control system built to give language models direct and flexible access to a real Chrome browser through the Chrome DevTools Protocol. Its main philosophy is minimalism: instead of imposing a rigid framework, it exposes a very thin bridge so the agent can perform browser tasks with almost no abstraction in the way. A defining part of the project is that the agent can write or extend missing helper functions during a task, which is why the repository...

...It analyses a library’s APIs, examples, and tests to propose harnesses that exercise parsers, decoders, or protocol handlers—precisely the code where fuzzing pays off. The system integrates with modern LLM-assisted workflows to draft harness code and then iterates based on build errors or low coverage signals. Importantly, it aligns with OSS-Fuzz conventions, generating corpus seeds, build rules, and sanitizer settings so projects can plug in quickly. Reports highlight what functions were targeted, how coverage evolved, and where manual hints could unlock more paths. The goal is pragmatic: shrink the gap between “we should fuzz this” and “we have robust fuzzing running in CI,” especially for understaffed maintainers.