Join this Gibwork Developer Hackathon bounty to create a new non-web-app use case for Gibwork using the SDK, CLI, or MCP.

This bounty is focused on practical developer workflows, automations, integrations, or tooling that demonstrate a compelling way Gibwork can be used outside of traditional web applications.

Bounty Description

The selected participants will be responsible for:

Designing and building a new Gibwork bounty use case that uses the SDK, CLI, or MCP in a meaningful and functional way.
Focusing this bounty on non-web-app development, such as developer tooling, automation flows, terminal-based utilities, AI agent integrations, backend workflows, local productivity tools, or other creative bounty concepts.
Implementing a working prototype that clearly shows how the bounty use case works, what problem it solves, and how Gibwork is integrated.
Documenting the bounty solution so another developer can understand the setup, usage flow, and expected output.
Providing a short demo of the completed bounty build, including the core workflow and successful execution.

Requirements

The bounty must use Gibwork SDK, CLI, or MCP as a core part of the implementation.
The bounty must be a new use case, not a minor variation of an existing demo.
The bounty must not be a web app, frontend dashboard, or browser-based product.
The bounty should solve a real developer, operations, automation, research, or workflow problem with a clear practical outcome.
The bounty submission must include clear setup instructions, dependencies, and steps to run or test the project.
The submission should be functional, organized, and understandable enough for basic reviewer validation.
Must attend at least 2 of the hackathon sessions on Discord.

What to Submit

A public GitHub repository URL for the completed bounty project, including all source code and a README.
A short written summary in the repository README or shared document explaining the bounty use case, why it is valuable, and which Gibwork toolset was used (SDK, CLI, or MCP).
Setup and usage instructions for the bounty project, including installation steps, environment variables, commands to run, and sample input/output.
A screen recording or demo video URL showing the bounty workflow from setup or execution through successful output.
Screenshots of the bounty project running, such as terminal output, logs, agent interactions, or generated results.
Any exported deliverables produced by the bounty project, such as output files, reports, generated artifacts, or shared document links, if applicable.

How to start

Submit to the Google form https://docs.google.com/forms/d/e/1FAIpQLSejpks7hItR6zBUXpdrwgUDrwvEcmnJj6nlFbUXKIyNkVVfag/viewform?usp=dialog
Check Discord (https://discord.gg/2577tTsRt) to see if you have been rewarded the Hackathon role.
Once rewarded the Discord role you can start the work.