Developer Workflow Demo¶
This demo is for users who want to evaluate SecondBrain as a builder surface after the personal-knowledge demo works. It stays offline-friendly and uses the public pattern and tool APIs instead of internal runtime modules.
What It Proves¶
- agent patterns can run without paid model keys
- tools are ordinary typed Python callables
- examples use public imports that are suitable for downstream builders
- the same surfaces can be covered by fast local tests
Command Path¶
Optional focused verification:
How It Uses Context, Memory, And Tools¶
examples/patterns/01_react_agent.pyexercises the public pattern libraryexamples/custom_tool/run.pyadds a custom tool with the public decorator API- both flows use offline-friendly provider behavior
Why It Is Different From Plain Chat¶
- you can inspect the code path directly
- tools are explicit callables, not hidden agent magic
- the same public surface can be tested offline
What Can Fail¶
- package not installed in the virtualenv
- Python path confusion
- importing from unstable internal modules instead of the public builder surfaces
- running the focused pytest command before installing dev dependencies
How To Debug¶
sb --helppython examples/patterns/01_react_agent.pypython examples/custom_tool/run.pypython -m pytest tests/patterns/test_run_cli.py -q -n 0- check
brain/patterns/__init__.pyandexamples/custom_tool/run.py
Next Steps¶
- read ../builders/add-a-tool.md to add a tool
- read ../builders/evals.md to add an evaluation loop
- read ../reference/patterns/index.md for the pattern API reference