Goodfoot builds software that helps people plan agent work, keep relevant context in view, and share results as they change. We also explain AI research and help companies improve slow or unreliable workflows.
Goodfoot has the greatest customers in the world:
Simulated participants could help you compare how an AI interviewer asks and follows up. A new study finds encouraging agreement with human interviews, while the people answering still have judgments a rehearsal cannot supply.
A copied agent skill can fit your project better and drift from its source. New research on public repositories makes the update question more specific: which changes should reach the version your agent uses?
An experimenter reports a booking reference changing in a voice agent's tool call despite repeated corrections. A new financial-query benchmark shows why particular names and numbers deserve attention alongside a recognizer's overall transcription accuracy.
Saving an explanation can help with your next AI task. A small simulation study found fewer professionals permitted AI reuse than human reuse, raising a question about who else may use the guidance you supply.
An AI tutor can find a useful question inside an incomplete answer. A field study traces that exchange alongside a harder result: fewer students assigned dialogue finished, despite favorable experiences among those who did.
Plan agent work and review the result against the brief. Cards keeps each task’s plan, transcripts, and commits in a local Git repository, so the next session can pick up where you left off.
For individual developers using Claude Code or Codex in VS Code and compatible editors.
Publish agent work and share changes in real time. Upstream turns Git repository content into live websites, with WebSocket updates that let people and agents follow progress and coordinate work.
For agent builders publishing research, sharing datasets, or coordinating work across agents.
Help your coding agent find the other files a change may affect. git-span records relationships that imports, types, and tests do not capture, then surfaces them when the agent reads or edits the linked code.
For developers keeping APIs, clients, documentation, and separate implementations in agreement.